Hi guys, you can also use $data.values()
Hello again,
As I mentioned above, this is not how a typical pagination would look like using the REST GET / HTTP Client Snap, since I'm not aware about any information in the response that can be used to set the Has Next and Next URL properties.
And since that you have the total number of pages in the info request, this approach will generate as many documents (requests) as you have pages.
If your parameters are static you can map them in the Map - Pages Mapper Snap and pass them in the JSON Splitter in the Include Paths section so you can use them in the REST GET Snap.
Please refer to the attached pipeline and let me know if this helps you.
Regards,
Aleksandar.
Thank You Aleksandar_A. It worked for me. I just wanted to check one more thing. When we create no of documents to hit the API that no of times. Does it run sequentially ?
I mean 1 document hits the API and once it gets the data then 2 document hits the API ?
If your groundplex node is running on Windows and is running as a network account that has been given access to the file share and file system folder and file, you can access using the file:// protocol. You need four slashes so the URI looks like file:////fs01-hou/Common/RDMetric/CARType.xls. Accessing local network shares was a primary use case as to why we set up our groundplex nodes on Windows boxes.
You need to set up SAMBA and access it using smb:// protocol
