Commit and revert patterns in multi-step workflows
ExpertControl when records are written to disk using Commit Records/Requests and Revert Record/Request for transaction-like safety.
What you'll learn
- When FileMaker automatically commits a record
- How to defer the commit until all fields are valid
- How to undo multi-record changes when one step fails
FileMaker does not have true database transactions, but Commit Records/Requests and Revert Record/Request give you control over when changes are persisted. Structuring multi-step workflows around deliberate commits and reverts — rather than relying on the automatic commit on navigate — makes scripts more predictable and safer.
When automatic commits happen
FileMaker automatically commits the current record when you navigate to a new record, change layouts, perform a find, or close the window. If you set fields in a script and then do any of these, the changes are committed whether you intended it or not.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo