Forum Discussion

Henchway's avatar
Henchway
Contributor
3 years ago
Solved

Pagination with HTTP Client

Hi, I’m not able to access the original document during pagination with the HTTP Client. This worked with the REST Client, but looks like it’s not possible any more. This is a needed feature when...
  • MattB's avatar
    MattB
    3 years ago

    In similar scenarios when the endpoint does not return the necessary info to determine the the ‘next page’ request directly I have used

    snap.in.totalCount

    I think in your scenario, the value returned by the above multiplied by the _pageSize pipeline parameter would equate to the Offest value you require for the next ‘next page’ request.

    Matt.

MattB's avatar
MattB
New Contributor II
3 years ago

In similar scenarios when the endpoint does not return the necessary info to determine the the ‘next page’ request directly I have used

snap.in.totalCount

I think in your scenario, the value returned by the above multiplied by the _pageSize pipeline parameter would equate to the Offest value you require for the next ‘next page’ request.

Matt.

  • Henchway's avatar
    Henchway
    Contributor
    3 years ago

    Hi Matt,

    thank you very much, I couldn’t solve it with snap.in.totalCount, but snap.out.totalCount did the trick.

    For people searching this in the future, here is the configuration. Specifically this is used with the Workday REST API.


    Best regards
    Thomas