Original request pack
The fictional Bracken Finch team has four records. Hours is numeric. Status and Owner are text.
| ID | Title | Status | Hours | Owner |
|---|---|---|---|---|
| 21 | Check pump | Open | 4 | Mara |
| 22 | Check pump | Closed | 7 | Ivo |
| 23 | Replace seal | Open | 2 | |
| 24 | Inspect casing | Open | 0 | Mara |
This is teaching data, not a customer export. Keep the IDs stable while changing a value for the second test.
Exercises and worked answers
- Show only open requests with at least 2 hours. The expected IDs are 21 and 23. In US syntax,
Filter(Requests, Status = "Open" && Hours >= 2)expresses both conditions. Filtering only Hours would wrongly include 22. - Display a fallback for the selected request’s blank owner. For ID 23, show Unassigned. That display must leave the source Owner blank. A visible replacement and a stored correction are separate tasks.
- Change only request 21 to 5 hours. Its closed neighbor 22 must remain at 7, and the row count must stay four. A title-only match or accidental New form mode can fail those checks.
- Try to save a blank required title. Retain the draft for correction and inspect the source. A success banner before the write is confirmed would mislead the next user.
For changed data, make request 24 have 3 hours. The first answer becomes 21, 23 and 24. A hardcoded table of the earlier two IDs is now wrong even though the first result was correct.
A project handoff
Build a browse-and-edit repair app, then give a colleague the filter condition, selected source ID and saved values. Include the blank-owner behavior and the failed-save test. Screenshots can show a screen state; the underlying row establishes the write.
The Power Apps course adds checked projects, fresh cases and original timed practice. Study gallery scope and forms before the project. The interview guide helps you explain the decisions. All connector effects in this workspace remain local.