POST Pagination in HTTP Client snap
A few month ago, I requested an option to pass the POST body content to subsequent calls. koryknick confirmed the request was already passed but there is still no any news. I already mentioned it's i...
Forum Discussion
Andrei_Y - There is a new PipeLoop snap that can help solve this. I have not tested this solution, but you should be able to put the HTTP Client snap in a child pipeline and call the child repeatedly with the output of the previous execution as input, allowing you to feed the new body content to the POST request. Simply call your child pipeline using PipeLoop (similar to Pipeline Execute) and you can set the End Condition when your return result array is less than your page size.
To help with the looping input, I also recommend using the Record Replay snap in the child before the HTTP Client snap to capture the data from your first execution an allow you to iterate the development - then remove the Record Replay once you have the looping logic working correctly.
Hope this helps!
The approach will work but it's not ideal. It requires passing previous results as input to a child pipeline in a loop and keeping everything in memory and complicates the implementation. A better solution would be to add an option to send and modify the body content for subsequent calls.
