I recently ran a batch update (using an action button) on all the items in a table view (with a filter), but despite the fact that there were several hundred rows (entities) showing in the table, only 100 of them got updated.
So I had to repeat the process several times (each time reducing the number of items showing in the filtered table).
Is this expected behaviour?
Is it a deliberate constraint to stop a batch action resulting in the browser freezing?
Hello.
There is no such limitation. And I failed to reproduce such issue. Iāve created āAssign to meā button and run it on several hundreds of entities. It worked correctly. Could you please share more details about how your button is configured?
UPD: we reproduced the issue, it is valid for some actions only and is a bug. Will release a fix soon.