I have a page with two paginations on it.
When using the pagination buttons it seems to effect other recordset paging as well.
Could this be because I have all three lists in the same server action? Is there a way to fix this without having to use three server connect actions?
It’s probably not so much that you are using one API for all three, but rather that they are all using the same offset parameter. If you give them their own offset, you should be able to control them distinctly.
And for what it’s worth, I see nothing wrong with three APIs, but they would still need separate offsets.
Thanks Ken, do I have to do that in the code somehow or is there a way in the UI?
You are using a query parameter to set the offset at the server (which is typical.)
So this means on your API, your paged query actions are looking for a $_GET.offset.
You will need to split this into 3 different query parameters, and yes you can do that in the UI. Each of your server connection actions on the front end will point to its own query parameter. And then on your API, each of the queries, will be paired with one of the $_GET parameters.
Brad, it would be best to have 3 separate server actions for these 3 paged results.
