Problem:
Currently, I am struggling with a table use case. I have 15 columns; Each row has a timestamp and specific number data columns which are linked to a category value in the same row. For each timestamp, I need to record each of the categories (so I have three rows for each timestamp). In total, I have 80 - 150 rows in one table per inspection. Therefore, I am exceeding the maximum allowed 100 rows in some cases.
The data in each row forms a single, coherent record that must not be split.
Tried workarounds:
1) I have tried to flatten the table and to put the categories into the header. This decreases the number of rows, but increases the number of columns. With 30 columns we would exceed the maximum number of allowed columns
2) At this point, the only possible solution for me seems to create an overflow page with a table containing the exact same layout. However, if we have less than 100 rows on the first table page, we need to fill in dummy data on the second page to complete the inspection (minimum of 1 data row is required).
Do you have any other suggestions on how this problem could be solved with SafetyCulture? / Any idea for a more convenient solution without the use of dummy data for the extra page?
Thanks for your support
Lukas