I am working on a checklist app. There are 80 different checklist items. This checklist can be repeated multiple times per day, and I want to capture each occurrence of the completion of the checklist. When the checklist is completed, I want to add a new record for each checklist item. I'll call the table that holds all the checklist results table B.
I have one table that has 80 rows in it (table A). In this table are two varchar columns that contain information about the thing that is being checked or not. I have created a gallery from this table. In the gallery, I have added three toggles and a Text field. My goal is to allow a user to change those controls, and when clicking submit, the values from those controls and the associated records from table A end up being written to table B.
Here it is:
I am running a ForAll(gallery.AllItems, Collect(collection_checklist, {.....})) to build a collection.
I then run Patch(table_b, collection_checklist)
What ends up happening is that it writes nulls to some of the new rows in table b where I know it should not be null. I have even built a new gallery from the collection that's created to make sure it does not have null values.
Static values or values from table A, which is the data source for the gallery, that get written to the collection all make it to table B. Many, but not all, of the values from the controls I added to the gallery do not make it into table B. If any of those columns are null in the sql table, they are all null in that same record, regardless of how they appear in the app. It seems to be able to pass the first 15-20, and after that it just loses it and they all go null.
Since some work and some don't, I assume that either it just can't handle this many records, or perhaps I am not building this optimally. Any ideas or suggestions would be greatly appreciated.
