GuidesPower Apps Patch() does not save or create the record
Power AppsVerified September 16, 2026
Power Apps Patch() does not save or create the record
Power Apps Patch() fails silently or errors almost always because of a missing required column, a type mismatch (text into a number/choice, or a string into a lookup/choice expecting a record), or because you patched a local copy/variable instead of the actual data source. Immediate fix: wrap the call in IfError(Patch(...), Notify("Patch failed: " & FirstError.Message, NotificationType.Error)) to surface the real error, then check the column’s logical name and pass the actual record or choice value for lookups/choices — for example {Value:"Active"} or a LookUp() result. Durable fix: confirm the user has create/update permission on the table and always patch the data source directly, not a collection or variable.
Common causes
- 1A required column is missing from the record you pass — Patch needs every mandatory field on create.
- 2A type mismatch: passing text to a number/choice column, or a plain text to a lookup/choice that expects a record.
- 3You patched a copy/variable instead of the data source, so nothing persisted server-side.
- 4A lookup or choice column was set with a string instead of the related record or the choice value.
How to diagnose
- 1Wrap the Patch in a Notify to surface errors: e.g. IfError(Patch(...), Notify("Patch failed: " & FirstError.Message, NotificationType.Error)).
- 2Check the column logical names vs display names — Patch uses the field names of the data source.
- 3For choices/lookups, set the value to the actual record (e.g. {Value:"Active"} or a LookUp() of the related row).
- 4Confirm the user has create/update permission on the table.