Work with calculations and custom functions

ADT can validate or evaluate a FileMaker calculation without storing it. Use those checks before placing an agent-authored formula in a field, script step, layout object, or custom function.

Validate a formula

Validation checks whether FileMaker accepts the calculation in the selected file and table-occurrence context. It catches syntax, function, and reference errors without saving the formula.

Validate this calculation in the Orders table-occurrence context. Explain any FileMaker error and do not save it.

The coding agent consults the FileMaker Pro 26 function reference for parameter order and behavior before validating the expression.

Evaluate a formula

Evaluation returns the result for the selected context. Use it to confirm logic, data types, and field references against the real file. A result can depend on the current record, related records, variables, privileges, and table occurrence, so record the context with the result.

An expression that validates successfully can still produce an unintended value. Evaluate representative cases before storing business logic.

Create or change a custom function

Tell the agent the function's name, parameters, expected result, and example cases. It resolves the active standards, validates the body, writes the custom function, and reads it back after commit.

Before renaming or deleting a custom function, inspect calculations that call it. FileMaker can accept a structural change that leaves dependent formulas broken.

Choose the correct context

FileMaker resolves unqualified field references through a table occurrence, not directly through a base table. Name the intended occurrence when a calculation uses fields or related data. Context-free calculations can be validated without one.