Type generation and data validation problems

Typegen reads metadata from the FileMaker layouts configured in an app's adt.config.json. Runtime validation then checks records against the generated schema.

Typegen cannot read a layout

Confirm that:

  • layoutName matches the FileMaker layout exactly.

  • The layout belongs to the FileMaker file bound to the app.

  • The account can access the layout and its fields.

  • FileMaker Pro 26.1 or later has the file open and Agent Access enabled.

Ask the agent to diagnose the connection before changing the configuration. A connection error and an unknown layout need different fixes.

Generated fields are missing

Typegen can discover only fields and portals placed on the configured layout. Add the required objects to the data layout, then regenerate the client. Do not add properties directly to files under generated/ or client/ because the next Typegen run replaces them.

Generated types are stale

Run Typegen again after the FileMaker database schema changes. This includes adding, removing, renaming, or changing a configured field, value list, or portal.

Updating the @adt/fmdapi JavaScript library alone does not require Typegen.

Runtime validation fails

A validation error means the returned FileMaker data does not match the generated schema or a project override. Compare the failing field value with:

  1. The current field definition in FileMaker.

  2. The field object placed on the configured layout.

  3. The generated schema.

  4. Any preserved override in the schema's root file.

Fix the FileMaker data or update an intentional override. Do not weaken validation globally to hide one unexpected value.

See Generate types with Typegen, adt.config.json, and Validation and transformation.