Forum Discussion
can you share the JSON output of this REST GET without pagination?
The best way to design “has next” and “next URL” I found is to use a mapper after REST GET to come up with an expression that will give you true for “has next” and next page URL for “next URL”. Once you figure those out then just copy those expressions back to the REST GET configuration.
I am able to get the condition which returns true if data exists for “Has next” which is “jsonPath($, “$entity.Items[*]”).length > 0”.
The “Next URL” has the correct URL, but is not triggering the URL as it is loading only the data for the Page = 1. The basic URL has the key at the header level. Does the Next URL attribute need to also have the key mentioned?
Not for HTTP Header. Have you tried to place a static URL for page 2 and see if it works?
I tried the Next URL with static URL to fetch the page 2, but it is not loading after the Page 1 data.
Related Content
- 2 years ago
- 4 years ago
- 5 years ago