Performance improvements for actions run on multiple rows
Addresses some performance issues with bulk application of actions within the app (via both multiple row selection and Ref actions that run another action on multiple rows). Previously running some actions in bulk led to higher total processing time than running each individually, in a way that worsened with increasing number of rows. This fix should address the scaling problem and also reduce the total time substantially for some actions in large tables.
This enhancement will be rolled out gradually. It is currently deployed to 100% of free users.
Bug fixes
None
Rollout changes
Item
Description
Bug
For the desktop design and new mobile framework (preview), update behavior of action “Data: add a new row to another table by using values from this row”. if the Row ID is specified and exists in the table to which you are adding the row, an UPDATE will be performed. Previously the action was blocked. This fix is being rolled out gradually.
New: Deployed to 100% of free users and 25% of paid users. Previous: Deployed to 100% of free users.
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
In addition, the AppSheet preview program lets app creators try out new app features that are not yet fully supported. For more details and to opt-in, see AppSheet preview program.
We have tested with free account where it is believed the new fix is deployed for this.
However, it looks like the new bugs are pushed into it, resulting in the expected odd behaviors which must be fixed right now.
See the gif image below.
With the legacy mobile UX, it is working fine. The new row having the existing key value is added to another table. However, executing the same action under the new desktop UX, the behavior of this action is changed. Actually “nothing is going to happen” …
Please please dig into the case.
We have posted the same claims in other post/thread, Please visit here as well.
I tried a batch run of a simple Action to Update Name on a Free account.
The Sync speed did not seem to be any faster than it has been in the past.
Does this update work in such cases?
Due to AppSheet’s specifications, we believe that sequential updates are done one at a time on the server. So it would be great if you could supplement us in which cases we can benefit from this.
@Koichi_Tsuji - Apologies for not responding sooner! Will escalate internally. Apologies for the inconvenience.
@takuya_miyai - I’ve passed on your question – there may be a delay as the AppSheet developer who is in the best position to respond is out of office for a few days. Apologies for that.
