IOS quick options for spreadsheet tables

I am new to Xcode but have been able to overcome all obstacles so far. Now I'm at a fork in the road and don't know which direction to go. The iPad app takes user input and then generates reports based on the input. I want to have so many columns in my reports that my entities have attributes and each attribute should have a column header and be sorted like a spreadsheet. UITableview seems to allow me to display a dynamic number of rows, and then if I have a custom cell with multiple hand-crafted labels mapped to attributes, I could sort the columns, having a bunch of buttons in the navigation bar that change how the table is displayed sorted. The problem here is that if I change my data schema,I need to redesign the cell view and write new code for the sort columns. HTML also seems like an option, but it feels and looks very different to the user. There is also a third party, but stubbornly, I want to create it myself. Could you guys give some advice on the pros and cons of each of my use cases? If I go first, is it possible (possibly) to write something that could automatically generate the layout in case a new attribute is added to the entity? Platform: iPad, language: swift, dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - will like the interface that allows users to create their own reports (don't want mine to become custom reporting)to mine to become custom reporting)to mine to become custom reporting)but it feels and looks very different to the user. There is also a third party, but stubbornly, I want to create it myself. Could you guys give some advice on the pros and cons of each of my use cases? If I go first, is it possible (possibly) to write something that could automatically generate the layout in case a new attribute is added to the entity? Platform: iPad, language: swift, dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - like the interface that allows users to create their own reports (don't want mine to become custom reporting)but it feels and looks very different to the user. There is also a third party, but stubbornly, I want to create it myself. Could you guys give some advice on the pros and cons of each of my use cases? If I go first, is it possible (possibly) to write something that could automatically generate the layout in case a new attribute is added to the entity? Platform: iPad, language: swift, dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - will like the interface that allows users to create their own reports (don't want mine to become custom reporting)give some advice on the pros and cons of each of my use cases? If I go first, is it possible (possibly) to write something that could automatically generate the layout in case a new attribute is added to the entity? Platform: iPad, language: swift, dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - like the interface that allows users to create their own reports (don't want mine to become custom reporting)give some advice on the pros and cons of each of my use cases? If I go first, is it possible (possibly) to write something that could automatically generate the layout in case a new attribute is added to the entity? Platform: iPad, language: swift, dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - will like the interface that allows users to create their own reports (don't want mine to become custom reporting)dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - like the interface that allows users to create their own reports (don't want mine to become custom reporting)dataset is not huge (rows under 100k, worst case), using master data needing flexibility on the reporting side - like the interface that allows users to create their own reports (don't want mine to become custom reporting)