Inspect a file's structure

Start a FileMaker task by asking the coding agent to inspect the objects involved. Inspection confirms the target file and exposes existing names, relationships, calculations, and dependencies before anything changes.

Choose what to inspect

Inspect this FileMaker file and summarize the tables, fields, table occurrences, relationships, scripts, layouts, and value lists relevant to the order-entry workflow. Do not change the file.

The agent can read individual catalogs or describe a named object in detail. A focused request is easier to review than a dump of every object in a large solution.

Schema and relationship views

Ask for a DDL schema when you need field definitions, table occurrences, and relationship structure in a compact text form. Ask for an entity-relationship view when the shape of the graph is easier to understand visually.

Show me the DDL and relationship paths for the Orders and Order Items table occurrences.

The relationships graph contains table occurrences, not base tables. Confirm both the base table and occurrence name when the distinction affects a layout or calculation context.

Read-only does not mean permission-free

Inspection does not commit a FileMaker change. Native schema inspection still requires a Full Access account because the FileMaker engine opens the schema through the same protected interface used for authoring.

Some live metadata and record inspection uses the open FileMaker Pro session instead. Those reads require the file to be open and the agent session to be authorized, but do not require ADT components unless the selected Web Viewer workflow uses them.

Verify the target

Before approving a change, check the file name, table occurrence, object name, and current definition in the agent's summary. If several files are connected, name the intended file explicitly.

See Work with multiple connected files and the filemaker operation catalog.