Check and update a file's ADT components

Updating the global toolkit does not change the ADT custom functions, layouts, or scripts already installed in a FileMaker file. Ask your coding agent to compare the file with the component bundle installed on your computer and reconcile any differences.

Check and reconcile the file

Ask the agent to inspect the file.
Copy
```
Check the ADT components in this FileMaker file. Compare them with the installed component bundle and show me what would change. Do not change the file yet.
```
The report separates missing components, components that differ from the installed bundle, and components that already match. It also reports the version recorded in the file when that stamp is available.
Review the proposed changes.

A reconciliation can create missing ADT components and rewrite ADT components that differ from the installed bundle. Matching components remain unchanged.
Ask the agent to reconcile the file.
Copy
```
Reconcile this FileMaker file's ADT components with the installed bundle, then verify the result.
```
After every component succeeds, ADT records the installed component-bundle and CLI versions in the file. A file whose components already match may receive only an updated version stamp.

Warning Reconciliation replaces changed ADT components Reconciliation treats the installed ADT bundle as authoritative. A custom edit made directly to an ADT-owned custom function, layout, or script can be replaced. Review the proposed changes and preserve any intentional customization before proceeding.

What reconciliation changes

Reconciliation is limited to the custom functions, layouts, scripts, and related objects declared by ADT's component bundle. It does not rewrite unrelated FileMaker schema or delete deployed Web Viewer app data.

The result reports every component created or rewritten and any component the installed bundle could not apply. A reported blocker means the file does not contain the complete component set even if the other changes succeeded.

Production files

Treat reconciliation as a FileMaker schema change. Use the same backup, testing, change-review, and maintenance procedures required for other changes to a production file. Review the proposed changes against a current copy before updating the production file.