I've sucessfully used the Looping With Actions method before, but I've come across a hitch which doesn't seem quite right?
I'm incrementing a counter on every iteration of the loop as well as calculating a new UNIQUEID(). The current counter is written back to the table row as usual and logic checks it doesn't go out of bounds so that the loop stops and doesn't run indefinitely.
For every increment of the counter and creation of a UNIQUEID(), I would expect that to be queued up as 2 record syncs in the top right hand corner, however, it only seems to sync 1 record up. Even if my counter has more than 10 increments, there is only one record to sync.
If I check the backend database, I get to see this synced data and the counter is whatever the last value would have been for that record which indicates it incremented that many times. Google Sheets has a cell history and the history only shows 1 update.
Now the problem is that I want to trigger a bot on each iteration of the counter. However the bot only triggers on the 1 update that is synced.
It seems like all the iteration stuff is being done on the client against a virtual table and then the final result is written as 1 sync. It triggers the bot...the bot runs fine (calls the Appsheet API) and finishes neatly. But I need all those updates to be counted as bot triggers.
Anyone have any idea if this is possible?
LinkedIn
Twitter
