Global variables in multi-user solutions
ExpertUnderstand global variable scope, per-session isolation, and when to use global fields instead.
What you'll learn
- The difference in scope between $$ global variables and global fields
- Why global variables cannot be used to share state between users
- When global fields are the right choice over global variables
Global variables ($$name) in FileMaker are scoped to a single user's file session on a single client. Each person logged in to the same hosted file has their own completely independent set of global variables. This is different from global fields, which are also per-session but stored in the database.
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.
Global variable scope: per-session, per-client
When User A sets $$token = "abc" and User B sets $$token = "xyz", each user's $$token is completely isolated. They cannot see each other's value. Global variables persist for the lifetime of the file session — they reset when the user closes the file.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo