Hide Object When -- Advanced Patterns

Beginner

Build sophisticated conditional UI using Hide Object When: multi-condition logic, combining with conditional formatting, user role gates, and performance considerations.

What you'll learn

How to write multi-condition Hide Object When expressions
How to gate visibility by user role or privilege set
How Hide Object When interacts with printing and PDF export
Performance considerations for complex hide conditions

Hide Object When is one of the most powerful layout features in FileMaker. A single calculation can conditionally show or hide any layout object based on record state, user role, global variables, or any combination thereof. Mastering its nuances -- what triggers a recalculation, how it interacts with tab order, and how to keep conditions readable -- is what separates amateur layouts from professional ones.

1/4

Multi-condition hide expressions

Combine conditions with AND, OR, and NOT. The object is hidden when the formula evaluates to a non-zero, non-empty result (truthy). Return 1 to hide, 0 or "" to show.

FileMaker Script

// Hide an "Admin Only" button unless the user is an admin AND in edit mode:
Get ( AccountPrivilegeSetName ) != "Admin" OR $$MODE != "edit"
// = hidden when NOT (Admin AND editing)

// Hide a "Delete" button unless record is a draft:
Contacts::Status != "Draft"

// Hide the portal "Add Row" button unless:
// - Record is not archived, AND
// - User has edit privileges
Contacts::Status = "Archived" OR PatternCount ( Get ( AccountPrivilegeSetName ) ; "ReadOnly" ) > 0

Layout Variables ($$Variables)Find Mode Layouts