Table of Contents Problem Statement Solution Overview Prerequisites Implementation Guide Step 1: Get Site and List IDs Step 2: Test with Graph Explorer Step 3: Initial Search Implementation Step 4: Handle Pagination Complete Code Examples Performance Considerations Conclusion Problem Statement After importing 10,000+ records into SharePoint using Power Automate bulk import techniques, we encountered Power Apps delegation limits that prevented effective searching and filtering of large datasets. There is the option of using Power Automate to get the results, however it adds more artefacts to a simple app designed for search.

Introduction When building Power Apps with SharePoint lists, you may encounter delegation warnings especially when using the Search function on large datasets. This post explains why delegation matters, how it affects your app, and practical workarounds to enable effective searching. The Delegation Problem By default, if you create an app using the built-in template connected to a SharePoint list, the gallery’s Items property might be set to: Search([@FolderMappingDetails], SearchInput1.Text, Title, Title) This triggers a delegation warning because the Search function is not fully delegable to SharePoint.