What the row limit actually means
Microsoft documents a default local-processing limit of 500 records for nondelegable queries, configurable up to 2,000. When the required operation cannot be delegated to the source, the app may evaluate only that retrieved subset. A record outside it can be absent even though the record exists and the user has access. Microsoft Learn: Understand delegation in a canvas app
That distinction changes the troubleshooting approach. A screen can appear correct because it returns some records. The acceptance question is whether it returns all the records that satisfy the business rule.
Trace the complete formula, not just the Filter
Microsoft's table-shaping documentation notes that arguments to functions such as AddColumns can support delegation while their output remains subject to the nondelegation record limit. A delegable inner filter is therefore not, by itself, proof that the final gallery expression is safe. Microsoft Learn: AddColumns and other table-shaping functions
For a review, write down the complete path: data source, filter, shaping functions, collection, sort and gallery. Identify where records become a locally materialized table. Also inspect startup code and intermediate collections rather than limiting the review to the visible control.
A simple test is to compare a known record in the source with the same record in every intermediate result. This creates a reproducible failure case instead of relying on a screenshot of a partly populated gallery.
Check the connector and column types
Delegation support is connector-specific. For example, Microsoft documents that SharePoint ID comparisons delegate for equality, but not for relational operations such as greater-than or less-than. The connector documentation also distinguishes complex column subfields. Microsoft Learn: Connect to SharePoint from a canvas app
This is why a generic formula copied from a different data source can be misleading. Review the functions, operators and actual column types together. Renaming a field or increasing a collection limit does not change what the connector can execute.
A practical reproduction and acceptance plan
- Choose a known matching record that falls outside the first local subset.
- Record the affected user, source permissions and exact gallery expression.
- Compare direct source retrieval with intermediate collections or shaping steps.
- Review every operation against the current connector documentation.
- Test the proposed change with representative data volume and each affected role.
- Compare the displayed results with an independently verified expected set.
Microsoft also suggests temporarily setting the app's data row limit to 1 to make nondelegable assumptions easier to detect during testing. Use a test copy and restore the intended configuration afterward. Microsoft Learn: Understand delegation in a canvas app
A successful test should demonstrate completeness, not merely faster loading. Counts, recently changed records and older matching records can each reveal a different failure.
Design around the question users need answered
Prefer a source query that retrieves the relevant working set directly. Decide which information belongs in the gallery query and which can be computed for a displayed record. Review any approach that first pulls a broad dataset locally and only then decides what the user needs.
Where the process needs a large aggregate, a complex relationship or a different security model, the right fix may include changing the data architecture. That decision should follow the requirements rather than a blanket rule that one platform is always correct.
W.I.S.E. can scope a review around the specific screen, data model and workflow involved. This guide is diagnostic guidance, not a substitute for testing the actual application and connector behavior in its target environment.
Sources & further reading
Official documentation checked for this release. Product behavior, licensing and feature availability can change; verify them for your environment.