We keep testing Automation.
Under simple scenario.
Change the column value for number, just increment by 1
When we run this as bot, it works as expected. Once we meet the condition (change in another column in the same row) the number fields is going to be incremented by Automation bot.
However, we run this process from action.
Then problem comes in.
For instance, now we see 1 in this number field and the backend cell holds 1 as well.
Hit action to run process.
Yes, the spreadsheet cell is change to 2. but this change is not pushed back to users device. So keep hitting the same action, nothing happen. Stay 2. It looks like process is running, but our device hold previous value of 1 on our screen, so hitting action to increment 1 is resulting 2 all the time UNLESS we manually sync the app.
Once we maually hit the sync, we will see the number hold in the backend. 2.
Then hit the action. THe number is refreshed to 3.
My understanding was the automation and process is happening on the backend. But on this scenario, the number being captured on the clients seem to be respected to run the process which causes unexpected issues.
When we run and fire the process by action button, we have to be careful.
But i think this should be reviewed and corrected, so that the proess will do the job, being triggered by Data Change event under the bot setting and the appsheet actions.
More strangely, as Appsheet long users, it looks strange as we will not see sync orange marks at the upper right corner. Yes, no data change is not initiated by action coupled with process…