Calculation context in FileMaker: how layout context affects results

Expert

A FileMaker calculation does not exist in a vacuum — it is always evaluated in a specific table context. Learn how layout context determines which table's records a calculation sees, and how unstored calculations can return different results on different layouts.

What you'll learn

What "calculation context" means and how it is determined
How the same field can return different values depending on layout context
How to audit and control calculation context to avoid unexpected results

Every calculation in FileMaker is evaluated from a table occurrence context — the active table in the relationship graph — and changing that context (by being on a different layout) can change the result of a calculation, especially for unstored calcs and those using relationships.

1/3

Understand table occurrence context

Every layout in FileMaker is based on a table occurrence — a node in the relationship graph. Calculations on that layout execute from that table occurrence's perspective, which determines which relationships are traversed.

TEXT

// Scenario:
// You have two table occurrences of the same "Customers" table:
//   Customers_Primary  (used on the Customers layout)
//   Customers_Archive  (used on the Archive layout)
//
// A calculation referencing "Contacts::firstName" from the
// Customers_Primary context traverses the Customers_Primary→Contacts
// relationship.
//
// The same calculation from Customers_Archive context traverses
// Customers_Archive→Contacts — a potentially different relationship
// with different match criteria.

Filter() for extracting specific characters in FileMaker Back to Calculations