Short answer
A delegation warning means Power Apps can't pass the entire query to the data source. The app evaluates up to 500 retrieved records locally by default, so matching records may be missing from larger sources, without an error. Check whether your formula is delegable for your data source and column type.
What delegation is
For a delegable query, the data source runs the query, for example a filter or a sort, and returns the results. Microsoft calls this delegation.
If any part of the query is nondelegable, Power Apps evaluates the whole query locally, and only on the records retrieved up to the data row limit. The app doesn't consider any records beyond that.
Delegation only exists for data sources that support it, mainly Dataverse, SharePoint, SQL Server, and Salesforce. Imported static Excel data and collections are already in app memory.
How to recognize the warning
Power Apps Studio flags delegation issues with a yellow warning icon on the control and a blue underline in the formula. Hover over the underlined part to read the delegation warning. The App checker lists every instance under Formulas.
A warning may be absent when you query a table already held in memory, such as a collection, even if not all records were loaded when the collection was filled. Check how the table was populated.
The data row limit
The default data row limit for queries that aren't delegated is 500. Find it under Settings > General > Data row limit, and you can raise it to a maximum of 10,000. At a high value, Power Apps Studio warns that retrieving and processing too much data can significantly affect performance.
Raising the limit can be enough for small data sources. It can slow down data retrieval, though, and still doesn't return complete results above the limit.
My tip for testing: Set the limit to 1 in a copy of the app while testing, and test with suitable data. A nondelegable query then evaluates at most one retrieved record, so you quickly see where results are missing. Reset the value before publishing.
Not to be confused with the list view threshold in SharePoint (5,000 items), a separate limit for queries in SharePoint that has nothing to do with the app's data row limit.
What is delegable
Check the data source and column type first. Filter, LookUp, and simple comparisons are often delegable. Sort delegates with a single supported column. For Search, First, text functions, and aggregates such as Sum or CountRows, the tables of the specific data source apply. A value that is the same for every record, such as a fixed number or a variable, can be passed as a constant. Check the connector's documentation for date functions such as Today().
Delegation at a glance
The most important differences according to Microsoft's tables (links in the sources below):
| SharePoint | Dataverse | SQL Server | |
|---|---|---|---|
Filter, LookUp, = | yes | yes | yes |
And, Or | yes | yes | yes |
Not | no | yes | yes |
Search | not listed | yes, for text | yes, for text |
StartsWith | yes, for simple text columns | yes, for text | yes, for text |
IsBlank | no | number, text, date/time, and GUID | no |
Counting (CountRows) | not listed | yes (see below) | not listed |
| Arithmetic on a field in a filter | not listed | no | +, -, *, and / on numeric columns |
"Not listed" means the function isn't in Microsoft's table for that data source. Assume that it isn't delegated.
What to keep in mind:
- SharePoint:
StartsWithdelegates on simple text columns, but not on subfields of choice and lookup columns. The ID column is only delegated with=, and<>isn't delegated for text. For person columns, onlyEmailandDisplayNameare delegable. - Dataverse:
Today()andNow()are explicitly excluded for date/time columns.CountRowsuses a cached value for the total count. Filtered counts and supported aggregates are limited to 50,000 rows. - SQL Server: Text functions only delegate in a specific notation, for example
StartsWith(Column, "Text")and not the other way around. Direct date filters for SQL Server don't work through an on-premises data gateway.
When in doubt, check Microsoft's current table for your data source.
Approaches in outline
- Choose delegable functions: Many warnings disappear when you replace a function with a delegable one that's good enough for your purpose.
- Keep calculations off the column: Calculate with the comparison value instead of the column.
- Use a separate pre-filter: Use a separate delegable query to narrow the data. Verify that the retrieved result is complete before processing it locally.
- Prepare the data: Some things can be prepared in the data source or with Power Automate so that the app only needs simple queries.
- Review the data source: Compare which search features, data volumes, and permissions your data source supports.
- Accept it deliberately: For tables that will definitely stay small (for example, a list of 50 locations), the warning isn't critical. Document this decision.
An example of how a warning appears and how it goes away. Orders is a SharePoint list with a single-line text column named CustomerText:
Filter(Orders, IsBlank(CustomerText))
Filter(Orders, CustomerText = Blank())
Comparing with Blank() leaves out empty strings (""). Use it only if that distinction fits your data.
Be careful with collections: Collect and ClearCollect load at most as many records from a connected data source as the data row limit allows. A collection doesn't get around delegation.
Sources
- Microsoft Learn: Understand delegation in a canvas app (opens in a new tab) (en-us, Oct 7, 2026)
- Microsoft Learn: Understand delegation in a canvas app (opens in a new tab) (en-us, Oct 7, 2026)
- Microsoft Learn: Understand data sources for canvas apps (opens in a new tab) (en-us, Oct 7, 2026)
- Microsoft Learn: Connect to SharePoint, delegable functions (opens in a new tab) (en-us, Oct 16, 2026)
- Microsoft Learn: Connect to Dataverse, delegable functions (opens in a new tab) (en-us, Oct 16, 2026)
- Microsoft Learn: SharePoint list view threshold (opens in a new tab) (en-us)
- Microsoft Learn: Connect to SQL Server, delegable functions (opens in a new tab) (en-us, Oct 16, 2026)
- Maximum of 10,000 in Power Apps Studio: checked in the German user interface on November 16, 2026