FileMaker script triggers: OnObjectEnter, OnObjectExit, OnObjectSave, OnRecordCommit

Intermediate

Script triggers fire automatically in response to user actions. Learn the four most important object and record triggers and how to attach scripts to them without creating infinite loops.

What you'll learn

The difference between OnObjectEnter, OnObjectExit, OnObjectSave, and OnRecordCommit
How to attach a trigger to a field or layout and pass context via script parameter
How to return False from a triggered script to cancel the action

Script triggers let FileMaker call your scripts automatically when a user enters a field, leaves a field, saves a field value, or commits a record — giving you precise control over validation and automation.

Stuck is a valid status

Need a second brain on this one?

If this lesson just collided with your real schema, script stack, or deadline, book consulting and turn the confusion into a concrete plan.

Book consulting

1/3

Understand when each trigger fires

OnObjectEnter fires when the user clicks into a field. OnObjectExit fires when focus leaves. OnObjectSave fires only when the value actually changes. OnRecordCommit fires when the entire record is saved.

FileMaker Script

# OnObjectEnter  — fires when the user clicks into the field
# OnObjectSave    — fires when the field value changes on exit
# OnObjectExit    — fires every time focus leaves (even with no change)
# OnRecordCommit  — fires when the record is committed (Enter, Tab out, new record)

# Returning False from any of these cancels the action

FileMaker Set Variable — scope, naming, and when to use it Perform Script on Server (PSOS): when to use it and how it works