No Pagination Support on REST Post Snap?
Hi everyone,
I am using the REST Get snap and it works beautifully for paginated data requests (using the Has Next boolean field and the Next URL field).
I noticed that for some strange reason th...
Forum Discussion
Kurt, did this get turned into a feature request that I could up-vote, or did you get a good alternative solution from support? I have the same issue with the Dropbox Business API List Members endpoint.
I have a workaround but it is rather unsatisfying. It requires three pipelines, nested two deep, and saves the cursor state between POSTS in a database table. I could avoid the issue with the cursor if Execute Pipeline supported recursion, but it doesn’t.
-Les
@llacroix - I can say that we have a new Snap Pack that is under development that supports paginated REST Post requests. I do not have the release timing yet for this particular feature, but it is definitely on the list of features to be included.
For now an acceptable workaround is to create a child pipeline that has the REST Post snap (and any other applicable logic) and create a triggered task for it. Then call that triggered task from your main pipeline using REST Get with appropriate pagination based on the response.
koryknick - was the Snap Pack supporting paginated REST Post requests ever released?
