Thanks all, now it’s clearer.
Currently, as you understood correctly, I do exactly this:
-
I manually select multiple rows using a [Select] column.
-
I set [Select] = “Yes” through a bulk action, which triggers multiple individual client-side updates. For example, selecting 100 rows causes 100 slow client-side updates.
-
After that, a Bot triggers and runs a grouped action on those selected rows.
From your explanation, it seems the suggested approach to improve this scenario is:
-
Temporarily capture the selection into a single row (e.g., using an EnumList column to store the IDs of selected rows).
-
Then use this single row’s EnumList as the input for the bot to quickly and efficiently update all the relevant rows in the backend.
Did I get this right?
Would this effectively avoid multiple client-side updates?
Thanks again!