Work with multiple connected files

A project can record several FileMaker files in adt.json. Each entry has its own target, optional account name, installed components, and live FileMaker session.

Connect another file

Ask your coding agent to add the file to the existing project:

Copy
Connect the Inventory Archive file to this ADT project.

The agent can discover an open file or use a local path or fmnet:// address you provide. Connecting records the file in adt.json; it does not copy or merge the FileMaker file.

Select the target

When only one file is connected, ADT can select it automatically. When several files are connected, tell the agent which one the task concerns:

Copy
Add the Status field to the Orders table in the Inventory file.

The agent passes the corresponding file key to the operation. If the request is ambiguous, it should ask rather than choosing a file based on which one happens to be open.

What the files share

Connected files share the project instructions, git repository, and project standards. If the project contains Web Viewer apps, they also share one vendored @adt/fmdapi JavaScript library.

They do not share credentials, FileMaker components, schema, records, or live authorizations. Update and verify each FileMaker file separately.

App bindings

Each Web Viewer app is bound to exactly one connected file in adt.json. Several apps may target the same file, and different apps in one project may target different files. Changing an app's file binding does not move schema, layouts, records, or app data between the files.