Work with value lists

FileMaker value lists provide choices for field controls and validation. ADT supports custom values and values drawn from fields.

Custom values

A custom value list stores an ordered set of literal values. Tell the coding agent whether order and separators carry meaning, and review the exact values before it writes them.

Create an Order Status value list with Draft, Submitted, Fulfilled, and Cancelled in that order, using the active project standards.

Field-based values

A field-based value list references one or two fields and can use relationship context to restrict its values. Confirm the source table occurrence, first and optional second field, sort behavior, and whether only related values should appear.

The relationship context affects which values users see. Verify the value list from a layout using the intended context, not only from its stored definition.

Modify or delete a value list

ADT can update a value list's name and definition or delete it. Before either change, ask the agent to inspect fields, layout controls, and generated schemas that reference it.

Deleting a value list does not delete field data, but it can remove a user's choices or invalidate a field's validation rule. Renaming or changing values can also require Typegen for apps whose configured layouts expose that list.

See Generate types with Typegen for generated value-list behavior.