SharePoint GetItems TopCount

[max81]

According to the Connector documentation, the "GetItems" operation with the "Top Count" parameter retriebes by default all items.

But the dev-documentation telling something else.


https://docs.microsoft.com/en-us/connectors/sharepointonline/#get-items

https://docs.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/guidance/working-with-g...

[manuelstgomes]

Hi @max81 

You're correct. If you don't define any value, the Get ITems will fetch the first 100. If you want to fetch more, you need to enable paging. To do that:

You can define the threshold (number of items per page), but I want to highlight the description:

"Retrieve items to meet the specified threshold by following the continuation token. Due to connector's page size, the number returned may exceed the threshold."

Can you please check if and let me know if you have any questions?

Cheers
Manuel

-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

[max81]

@manuelstgomes thanks.

I know that "paginaging" option.

But still the documentation is not correct.

Also there is no possibility with this action to get more than 5000 items back, because there is no "nextlink" in the response.

That's why I use the _api from SharePoint (Send HTTP request to SharePoint-action) to get all items back, if I have to - but that's not so easy to use for our standard "citizen developer".

[manuelstgomes]

HI @max81 

It's a lot of data indeed. I'm sure you thought about this, but is there a way you can segment the data. For example, do multiple fetches based on time periods or any other field in your data that could break things down into smaller pieces?

I know this could be too much, but you can even think about breaking into groups of 1000 based on the ID number. I know this is trying to do pagination "by hand", but if it's not working with the "next link," we need to figure out a workaround. 

Cheers
Manuel

-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

[max81]

I have several workarounds, depending on the business case:
• Filtering with ODATA
• Using the "Send Http Request to Sharepoint" with _api to get all list items (and then I get also a "nextlink")

My problem is, that I think the documentation is wrong and that should be fixed. I got users that ask me that and I also saw some users with this question here in the community.

[manuelstgomes]

HI @max81 

You're right. Having good documentation is essential. I would submit a bug so that Microsoft can take care of that.

https://powerusers.microsoft.com/t5/I-Found-A-Bug/bd-p/BugFound

It's well worth to correct

Cheers
Manuel

-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

[max81 · Accepted solution]

Bug reported:
https://powerusers.microsoft.com/t5/I-Found-A-Bug/SharePoint-GetItems-TopCount-Documentation-not-cor...