Hello
The problem we are facing is a GQI query which is sending back 2000 rows at least and first call seems to make a full load and then pagination is made on the dataset. So it takes a lot of time.
i would like to handle pagination on server side by myself but problem is that pagination properties available in payload of GetNextQuerySessionPage request are not available in the GetNextPageInputArgs argument of GetNextPage GQI function.
May be i am using the wrong class to get that ?
the answer which would say we should filter first to have less data is not accepted 🙂
thanks
As this question has now been inactive for a very long time, I will close it. If you still want more information about this, could you post a new question?
Hi Julien,
Indeed, in the example the counter will be incremented between two calls. The counter is kept alive within the class/object. The object is staying alive during the lifecycle of the query. Only when all pages are fetched or the the session is closed it will destruct the object.
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer (using the ✓ icon) to indicate that the question is resolved?