These settings should do it, as long as you set the offset to 0 in the "query parameters" section, you should be in the clear
It seems like this approach does allow me to reach next page, but instead of fetching the rest of the dataset, it just re-fetches the same data from the 1st fetch. So it looks like the Has next expression is working, meaning it evaluates to true, but isn't able to pull the rest of the data. It seems like I'm failing at notifying the API that I want the 2nd batch onwards. So if I start with offset=0, then I'm not able to increment that value.
These settings should do it, as long as you set the offset to 0 in the "query parameters" section, you should be in the clear
I've changed the '100' to '1k', since that's the API batch size, and it worked like a charm, thank you ddellsperger !
I still have some questions if I may, since I'm not too familiar with the 'snap.out' property. I tend to fail at trying to read the values of this property during validation and see what it holds to get a better understanding, is that impossible? Another thing is the $entity property being accessible in the 'Has Next' clause but not in the others, can you elaborate on that please?
The snap properties have documentation available here https://docs-snaplogic.atlassian.net/wiki/x/ovYV (these are built-in properties for all snaps). As far as the reason some properties are available on the input and or output, at least the design of this snap anything that's used for the initial request to the endpoint will not support the output document paths, the only places where we support the output document path is in the pagination parameters as those will typically rely on the output of the result in order to operate. Generally snaps will not use the output document for evaluation mostly because most snaps end their execution cycle at the point of receiving a response from the servers, then they are set to format to the final output document from there.
