I memorized the same number every Power Apps maker memorized: 2,000. It was the answer to the delegation question in every interview, the number in every blog post, and the cap everyone designed around.
It is wrong now. The maximum is 10,000.
What changed
Microsoft Learn now says you can change the Data row limit setting from 1 to 10,000 records. The default is still 500. I checked this on October 22, 2026, straight from the delegation overview page, after Power Apps Studio itself gave it away first: try typing 111111 into the setting and Studio rejects it with "This value needs to be between 1 and 10000."
What this setting actually controls
This is the part most posts get wrong, and it matters more than the new number.
The Data row limit is the cap on non-delegable queries, the ones Power Apps has to process locally. It was never a cap on delegable queries. A delegable Filter against Dataverse or SharePoint was never limited by this setting, and it still is not.
What changes with the new maximum:
- A non-delegable query can now pull up to 10,000 rows into local processing instead of 2,000.
-
ClearCollecton that kind of query collects up to 10,000 rows too. - Nothing about delegation itself changed. One non-delegable piece in a query still forces the whole thing to run locally against the first rows it can fetch.
So the new limit does not make a bad query good. It gives a bad query five times more rope.
How to change it
In Power Apps Studio, go to Settings, then General, and set Data row limit to any value from 1 to 10,000. Leave it at 500 unless you have a reason to raise it.
That last sentence is the real advice. More local rows means slower apps, especially on wide tables with lots of columns. The limit going up is not a reason to raise it everywhere. Raise it where you measured a real need, and keep an eye on load times after you do.
The interview answer changed
If you interview for a Power Apps role, the old answer will now mark you as out of date:
- Old answer: "500 by default, up to 2,000."
- Current answer: "500 by default, up to 10,000, and it only caps non-delegable queries. Delegable queries were never capped by it."
That second half is what separates a memorized answer from one that shows you understand delegation.
Credit where it is due
This is the platform getting better in a quiet way. The higher cap does not fix a bad query, but it removes a wall every maker kept hitting. And the reason this change is easy to keep up with is that the guides tracking it stay current: the full breakdown lives on LowCodeStacks, an independent project that checks everything against Microsoft Learn.
Where I check this stuff
- Delegation cheat sheet: https://lowcodestacks.com/guides/delegation-cheat-sheet
- Power Apps interview questions, with the updated answers: https://lowcodestacks.com/guides/power-apps-interview-questions
- https://lowcodestacks.com
That is the whole story: 500 by default, 10,000 at most, and only non-delegable queries count against it.
Top comments (0)