Have to call it a night Neil but thought i would share my thought process in case it helps, maybe a few other members may wish to chirp in
The paged query returns a number of additional information which is not included in the standard query
I dont think this can be generated via a query only
Not sure how we can reproduce that in total but thought perhaps if we could feed the data module via the custom query and the additional info via a separate object to “feed” the paginator
The custom query is easy and produced the correct output but without paging
So i have the idea of creating a custom object within a set value like below to duplicate the required data
and populate it with the required JSON (hard coded values at this stage for testing)
At present i have an output of:
Now it the time to confess JSON is not my strong point
In the latter query part the JSON does not appear correctly formed and I am struggling to resolve that
Secondly, at this stage i have no idea how to insert live values for the hard coded values when i get it right!
But it is a start.
If you have any ideas, feel free or if you./ anyone thinks this approach is a lame duck or has a better idea then I would prefer to know now than later
Alternatively there may be a way of doing this by directly manipulating the query parameters here, perhaps via the state manager (would need a custom paginator):