That worked!! Thank you @j.angelevski
Also, is it possible we can map the upperlimit to the lowerlimit?
so that whenever, ApprovalType ==“Greater than equal to”, $lowerlimit should have the value of $upperlimit which works along with the filter out of upperlimit.
Appreciate your help @j.angelevski 😀
Thanks,
F.
Yes, it is possible to map the upperlimit to the lowerlimit, you can try with the following expression:
jsonPath($, "Project[*]").map(val => val.ApporvalType.toLowerCase() == "greater than equal to" ? val.extend({lowerlimit: val.upperlimit}).filter((v, k) => k != "upperlimit") : val)
Here I’m using the extend() method, with this you can add a specific field to the object or overwrite an existing one with a new value. In this case the upperlimit value will be assigned to the lowerlimit field, resulting in overwrite of that same field.
Hello adityamohanty,
You could with the following approach:
sl.range(1,$page_count+1,1).map(x => {"page":x, "page_size":$page_size})
I chose this approach since I'm not aware of the format of the response of the models endpoint. If there are pagination information, you could achieve the same using REST GET Snap or HTTP Client Snaps with proper pagination enabled.
You can refer to the pipeline attached below and let me know if this helps you.
Regards,
Aleksandar.
Hello Aleksandar_A
Thank you so much for the reply. I understood your approach but not sure how does it help to run it in a loop because following "Has Next" and "next url" is blank in REST GET request in your pipeline (Screenshot attached)
And I have few parameters and token which has been used to call the API and I can successfully call it out through mapper and used in REST GET snap. But when passing JSON Splitter as per the suggestion between Mapper and REST GET to split the array of pages, it's not capturing my parameters and token value to the REST GET Input. The only output of JSON Splitter, I can see is Page & Page Size. Any advise ?
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 ?
Load sql query data to csv file and send this file in email as an attachment | SnapLogic - Integration Nation - 20903