How layout context determines related records

Intermediate

Understand how the current layout table occurrence and current record together define which related records are visible — and how context shifts when you navigate or run scripts.

What you'll learn

How the current layout context and current record together define the relationship scope
What happens to context when you use Go to Related Record or Perform Script
How to deliberately switch context to work with a different table occurrence

In FileMaker, every layout has a context — the table occurrence it is based on — and every field, portal, and calculation evaluates relative to that context and the current record within it.

1/3

Understand that each layout has one context

When you open a layout, FileMaker sets the context to that layout's table occurrence. All field references, summary calculations, and portals evaluate relative to that TO and the current record.

FileMaker Script

# Layout "Customers" (based on TO "Customers"):
# - Customers::Name  → shows current customer's name
# - Orders::Total    → not directly accessible; must be in a portal
#                       or accessed via a relationship
# - Count(Orders::OrderID) → counts related Orders for THIS customer

# Layout "Orders" (based on TO "Orders"):
# - Orders::Total   → current order's total
# - Customers::Name → shows the PARENT customer's name (via relationship)

Primary keys and foreign keys: UUID vs serial number Organizing the Relationships Graph: layout, colors, and notes