A form update
At the fictional Sedge Line Workshop, request 84 needs its estimated hours changed from 3 to 5. Request 85 has the same title and must remain at 3. The owner and description on both requests must stay unchanged.
Bind the edit form to request 84, enter 5 and inspect the draft. Before submission, the source still has 3. Submit the form through its supported behavior, then read request 84 from the source again. A changed input field alone cannot establish a successful write.
New mode creates a record. Edit mode changes the selected existing record. Switching modes accidentally can create a second request while leaving 84 untouched. Include the source ID and row count in your checks.
Patch and record identity
This original US-syntax example updates one numeric field:
Patch(Requests, LookUp(Requests, ID = 84), {Hours: 5})
The base record identifies the source row. Defaults(Requests) would express creation instead. If your task authorizes editing 84, a new row with the same title is still wrong.
For a simple single-record edit, a form can expose the fields and validation together. Use Patch when the app’s behavior needs an explicit data operation. Neither route permits replacing unrelated fields merely because the target value is correct.
Failure and read-back
Test a blank required field, a read-only source and the lesson’s supplied failed-write case. A success message should follow confirmed success; an error should retain enough input for correction. A retry also needs a check for an earlier successful creation so it doesn’t duplicate a record.
The local course models selected form and connector outcomes. It doesn’t prove production permissions, network reliability or every concurrency policy. Continue with gallery selection, the data-source guide or the Power Apps course.