Fix the Power Apps delegation warning
A blue squiggly underline in the formula bar means part of your formula is non-delegable, so Power Apps only pulls the first 500 rows (up to 2000) from the data source and runs that formula locally — records beyond the limit are silently missed. Immediate fix: replace non-delegable functions with delegable ones (Filter() with =, <, >, StartsWith() instead of Search() or non-delegable expressions), and move computed conditions out of the query into a precomputed column or variable. Durable fix: filter on the server first, then do non-delegable work only on the smaller result. Raising the row limit to 2000 is a stopgap, not a real solution.
What the warning actually means
Delegation is when Power Apps pushes the work of a Filter, Sort or lookup down to the data source (Dataverse, SQL, SharePoint) instead of pulling rows into the app and processing them locally.
When a function or operator is not delegable, Power Apps only downloads the first N rows (500 by default, up to 2000) and runs your formula on that subset — so users silently miss records. That is what the blue underline is warning you about.
How to tell if a formula is delegable
Look for the blue squiggly underline and the warning icon in the formula bar. Hover it to see which part is non-delegable.
Delegation support depends on the data source: Dataverse and SQL delegate the most; SharePoint and Excel delegate far fewer functions.
How to fix it
- 1Replace non-delegable functions with delegable ones: prefer Filter() with =, <, >, StartsWith() over Search(), in or non-delegable expressions.
- 2Move computed conditions out of the query: pre-compute a column or a variable instead of calling a function inside Filter().
- 3Filter on the server first, then do non-delegable work on the small result (e.g. Filter on a date range, then sort in the app).
- 4If the table is genuinely small, raise the data row limit to 2000 (Settings > General) — but treat this as a stopgap, not a fix.