Hello all
I am happy to keep this discussion alive. I really believe something changed at Adalo because the behavior of my screens changed after a year in use.
My app is working now and here is what I have learned…
Do not update a property in a collection with a countdown timer when the property exists in the filter for the custom list.
I hope people prove me wrong, but I have worked around this by making sure that my custom list filters are not involving any updates through the timer.
Of course, I am producing bigger lists but it works. I was trying to filter the lists to be more efficient. In my case, I was just trying to set a T/F property for records that were already T to F…just clearing a print queue.
But the T/F Property was involved in the filter for the list.
Once I took that out, it worked. Instead of filtering on 20 records that are T and change to F, I just run through 1000 and turn them all to F. It seems to be fast enough for my users and it works.
Another thing I learned along these lines, is the production of new records. I use a countdown timer to run through records and create a new print record for each one.
This was producing more print records than original records. (see post above)
Again, the filter issue came into play. In the click actions, I first marked the original record “processed” with a T/F and then created the new record.
But the original record was involved in the filter for the custom list. So I changed the order of my click actions to create the new record before marking the original record as processed.
Then no more additional records being produced. Feel free to call me stupid for doing this in the wrong order.
Anyway, thanks all for your help!