Duplicate titles
The fictional Harbor Wren team has these requests. Their statuses are stored as the literal values Open and Closed.
| ID | Title | Status | Priority |
|---|---|---|---|
| 42 | Replace latch | Open | 2 |
| 57 | Replace latch | Closed | 1 |
| 63 | Inspect frame | Open | 1 |
Filter(Requests, Status = "Open") returns IDs 42 and 63. A title-only LookUp for Replace latch can return a record, but it doesn’t express which ID the request author intended. Identify 42 explicitly when that is the record you must change.
Set the gallery’s Items formula to the requested table. Select its row, inspect Gallery1.Selected.ID, then bind the form’s Item to that selected record. A filtered list and a form that still shows an old selection can disagree. Test the selection after the filter changes.
Empty result and record scope
LookUp returns blank when no record matches; Filter returns an empty table. Decide what the app should show in each case. A blank owner on a matching row is a third case and needs its own test.
Within a gallery template, ThisItem refers to that displayed row. A formula outside the template needs the intended selection or record scope. When a nested formula introduces another record, name the scopes clearly instead of assuming every ID refers to the gallery’s row.
A tiny table cannot prove a large connector query is complete. Place a matching test row beyond the local row limit and inspect the connector’s supported operations before relying on the absence of a delegation warning. The delegation guide follows that failure.
Practice
Change the requested status to Closed. The expected gallery now contains ID 57, and a form previously bound to 42 must not silently edit it. Return to Power Apps practice for a checked-data checklist, or study forms and Patch before saving a change. The course uses local records and a supported canvas model.