I switched over from automatic to manual for my getRows query so that I have more control over when to re-run the query when variables change that affect the query. But I noticed that the server side pagination stopt working as it should. Whenever I click the next button in my custom collection, the query should be triggered to get the new results. This doesn’t happen anymore. I have to run it manually.
I’m still stuck on this.
I’m considering creating my own pagination with buttons so that I can at least push a new release. Seems weird that pagination is only possible if the resource query is set to automatic.
Hi @Steven_W this feature request is in our backlog. We don't have an eta yet, but I'll post here if it ends up getting prioritized
Currently, the paginated query can be manual, as long as you are using watched inputs. The endless loop behavior sounded like it was due to the total row count triggering on success of the paginated query, which then caused all of the table properties to re-evaluate. It's my understanding that as long as total row count & get rows are separate, you can have a manual query for pagination