{"id":1987,"date":"2026-10-16T16:56:44","date_gmt":"2026-10-16T15:56:44","guid":{"rendered":"http:\/\/www.stuartroberts.net\/?p=1987"},"modified":"2026-10-16T18:19:13","modified_gmt":"2026-10-16T17:19:13","slug":"power-apps-sharepoint-id-delegation","status":"publish","type":"post","link":"https:\/\/www.stuartroberts.net\/index.php\/2026\/10\/16\/power-apps-sharepoint-id-delegation\/","title":{"rendered":"Power Apps & SharePoint ID Delegation"},"content":{"rendered":"\n

Short #23<\/strong> – The SharePoint ID delegation trap<\/p>\n\n\n\n

Need to retrieve SharePoint items where ID > 1000<\/code>? There’s a catch.<\/p>\n\n\n\n

Although SharePoint’s built-in ID<\/code> column is numeric, the ><\/code> operator isn’t delegable for it in Power Apps. You’ll see the blue delegation warning on this formula:<\/p>\n\n\n

\nFilter(Projects, ID > 1000)\n<\/pre><\/div>\n\n\n
On large lists this can return incomplete results, because Power Apps only processes the first 500 records by default (2,000 at most if you raise the data row limit).<\/p>\n\n\n\n
What’s the workaround?<\/h3>\n\n\n\n
Filter on the server with Power Automate. In the Get items<\/strong> action, put this in Filter Query<\/strong>:<\/p>\n\n\n
\nID gt 1000\n<\/pre><\/div>\n\n\n
SharePoint applies the filter before returning anything. Turn on Pagination<\/strong> in the action settings if more than 100 items can match. If you need $select<\/code> or $expand<\/code> control, use Send an HTTP request to SharePoint<\/strong> instead:<\/p>\n\n\n
\nGET _api\/web\/lists\/getbytitle('Projects')\/items?$filter=ID gt 1000\n<\/pre><\/div>\n\n\n
Keep the returned set reasonably small (filter further or use $select<\/code> to trim columns), as flow responses have size limits.<\/p>\n\n\n\n
I\u2019d avoid adding a duplicate numeric column just to filter on, since you then have to keep it in sync.<\/p>\n\n\n\n
Two other options<\/h3>\n\n\n\n