Performs a script before a record that has been changed is committed.
Actions that cause a record to be committed include:
- a user changes data in a record and moves to another record
- a user changes a record and immediately accesses the Manage Database dialog box
- a user presses the Enter key
- a user clicks the layout outside of the activated record after the record has been modified
- script steps that move focus to a different record if the previous record was modified
- a script performs a Commit Records/Requests script step
When the script runs
Before the event has been processed.
Modes in which the trigger can be used
Browse and Find modes.
You can use the Exit Script script step within the triggered script to return True or False.
- True: The event that triggered the script proceeds.
- False: The event that triggered the script is canceled.
|FileMaker Cloud products||Yes|
|FileMaker Data API||Yes|
|Custom Web Publishing||Yes|
Originated in version
- In a portal that displays records from a related table, moving from record to record inside a portal does not cause a commit; those changed records are committed when the focus leaves the main record to which they are related.
- This script trigger activates only when there are uncommitted record changes.
- Exiting a record that had keyboard focus activates this script trigger only when the record being exited was changed.
- See Actions that don’t activate script triggers for a list of other actions that do not activate this script trigger.