A missing request
The fictional Larch Quay team has 620 repair requests in source order. Request 614 is the only open request whose title starts with Z. In this teaching example, the app’s nondelegable row limit is 500.
A query evaluated locally over that prefix cannot inspect request 614. Filtering afterward doesn’t move that request into the first 500 rows. The empty gallery therefore fails the business request even though the formula produces a valid empty table.
Use a connector-supported predicate or redesign the query boundary. Compare the returned IDs against the supplied source evidence. Raising a limit can make this one example pass while leaving a larger source vulnerable.
Connector scope
Delegability depends on the connector, column type and expression. A local collection is already in memory; a formula over it doesn’t prove remote support. For SharePoint, the current connector table distinguishes text from complex Choice and Lookup fields. A plain text prefix test cannot be generalized to those subfields.
The current English Microsoft documentation lists a default of 500 and a configurable ceiling of 10,000. Older translated material can show an earlier ceiling. Check the actual environment’s setting and current connector documentation before applying that number to a live tenant. The course identifies its modeled limit; it doesn’t discover your organization’s rollout state.
A test record beyond the prefix
Retain request 614 as your exception. Test the same business condition with a smaller local limit, inspect the expected source ID and compare a supported query with the incomplete query. Don’t claim success only because a warning disappeared.
The practice connector is local. Its disclosed supported operations teach the query boundary rather than reproduce every server query planner. Use the gallery guide for record selection, data sources for model differences and the Power Apps course for checked tasks.