Avoid SharePoint list view threshold errors in Power Automate
Diesen Beitrag auf Deutsch lesen
Use Filter Query in Get files (properties only) to return a targeted SharePoint Online subset instead of an entire growing library.
TL;DR
Power Automate cloud flows using SharePoint Online Get files (properties only) can hit a list view threshold once a library exceeds 5,000 items. Add an OData Filter Query under Advanced parameters to restrict the initial REST request, and put the filter that returns fewer items first as the library grows.
Original by Charles, on Charles Lakes. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Add an OData Filter Query to Get files (properties only) so the flow retrieves only the SharePoint files it needs.
- Makers: Order filters with the more selective column first to reduce the chance of another threshold failure as the library grows.
Frequently asked questions
How do I fix a list view threshold error in Power Automate Get files properties only?
Add a Filter Query in the action's Advanced parameters. It restricts the SharePoint REST request to the required subset of files.
Why does Get files properties only fail after a SharePoint Online library grows past 5,000 items?
The action can attempt to retrieve too many library items in one HTTP GET request. That request can exceed the SharePoint list view threshold.
Which filter should come first in a Power Automate SharePoint OData Filter Query?
Put first the filter that returns the smaller set of list items. This reduces the query size as the document library continues growing.