Forum Discussion
Power Automate 'Send an HTTP request to SharePoint" only returning 300 rows of data
- Apr 09, 2024
Hello humphriesk ,
I wrote this blog post a few years back, I hope it helps (and still works!) https://pwmather.wordpress.com/2020/09/20/handling-pagination-in-powerautomate-sharepoint-http-flow-action-for-projectonline-flows-office365-automation-workflows-powerplatform-poweraddicts-nocode-lesscodemorepower-msproject/
Paul
- humphrieskApr 11, 2024Copper Contributor
Paul_Mather -- Thanks for following-up! Your post has me 90% of the way there, but I'm hung up on this:
Given this schema
{"type": "object","properties": {"value": {"type": "array","items": {"type": "object","properties": {"ProjectId": {"type": "string"},"ProjectName": {"type": "string"},"ProjectWorkspaceInternalUrl": {"type": "string"}},"required": ["ProjectId","ProjectName","ProjectWorkspaceInternalUrl"]}},"odata.nextLink": {"type": "string"}}}In the Do-Until loop, the first page returns an odata.nextlink valueso the subsequent actions complete.
But the for the 2nd loop, the final page returns no data at all -- not even a null value, so the parse operation fails:
And of course, subsequent actions also fail -- including the condition that checks for a Null odata.nextlink value.
Your thoughts?
- Paul_MatherApr 12, 2024MVP
Hello humphriesk ,
It's been a long time since I looked at that and I don't have it set up or an environment with enough data to test but could you add a condition check before the parse action, if no data is returned, skip the parse / next actions.
Paul
- humphrieskApr 23, 2024Copper Contributor
Hi, Paul_Mather -- I tried a few variations, and here is what I arrived at. I couldn't get the parse JSON to give me any usable results , so I substituted a Compose check of the odata.nextLink, followed by parallel actions. If the Compose is successful, great. If it fails, then I assume the pagination is "Completed".