FrameReady → Acumatica

Sample request

Contract endpoint(s) for catalog

Check contracts to merge. Select all / None (.env) apply to the list below. Choices sync to the server for the whole team; the browser keeps a copy for speed. Static hosting without dev-server.mjs falls back to this browser only.

— List endpoints first —

Entity/table list

Field mapping

FileMaker fields

Mapping JSON (Acumatica path → FileMaker field: id, name, type)

OData schema

If FILEMAKER_ODATA_METADATA_URL is set in .env, this tab loads that FileMaker Server $metadata via the dev server (optional Basic auth in .env only). If sample loads return 404 / Not found, add FILEMAKER_ODATA_DATABASE (the hosted database name from Admin Console — not entity types like Contacts_) or use …/v4/YourDatabase/$metadata. When the schema is slim, use Load sample per entity set or Load fields (all entity sets) to pull a $top=1 OData row and merge field names into Entity types. Otherwise it loads Acumatica $metadata for the current session contract. Use Reload after you connect or change settings. If the live request fails, the app falls back to sample odata-sample.xml in this repo.

Claris FileMaker OData API guide: Get database names (GET …/fmi/odata/v4) · Get list of tables (…/v4/database-name, system tables e.g. FileMaker_Tables) · Get metadata (…/v4/database-name/$metadata — rich annotations when the path includes the database).

Filter

FileMaker databases, tables & layouts (GET …/v4, FileMaker_Tables, occurrences)

Entity sets (FileMaker OData resources — URL segment per layout/occurrence)

Table names (FileMaker base tables)

Enumeration types (value lists)

Entity types (properties & navigation)

Mapping editor

Select a profile to edit, or click + New to create one.

Name

Description (optional)

FileMaker database

Primary FileMaker table (context)

Primary table dashboard fields (optional)

One row per OData process; all rows run in order on POST /api/mapping-exec
Step — drag to reorder	HTTP method	Acumatica entity	FileMaker table	`$expand`

Developer $select, OData path, test JSON

Optional $select (PUT/PATCH URL)

OData path override (optional)

Test record JSON (mapped FM field names → values)

FileMaker integration

Field mapping still loads definitions from fm-fields/<layout>.json when that file exists (same name as the chosen table/layout). Otherwise use the Web Viewer URL or FILEMAKER_FIELDS_JSON on the API tab.

Insert from URL — script steps (XML)

This is ordinary UTF-8 XML as text (FileMaker fmxmlsnippet shape) — not a locked binary. Use Copy XML (UTF-8 text) for paste utilities, snippets apps, git, or any tool that stores clipboard text. Download XML is the same bytes as a file. The dev server builds this XML via POST /api/fm-snippet-xml so your integration token stays on the server until it is embedded in this script (OAuth in the browser is sent in that POST body instead). Generated from this profile’s method, entity, and $expand. The $url in the snippet is this app’s base + /entity/… (override with APP_PUBLIC_URL in .env if FileMaker needs a different host than the browser). FileMaker’s cURL hits node dev-server.mjs, which proxies to ACUMATICA_BASE_URL. For POST/PUT/PATCH, JSONSetElement lists only mapped Acumatica fields (with a FileMaker field chosen), using Table::field. You can also click the box below and ⌘+C / Ctrl+C.

FrameReady → Acumatica

Sample request

Entity sync

Field mapping

OData schema

Mapping profiles

Mapping editor

FileMaker integration

Secure proxy to Acumatica

Field mapping

Sync details

Configure match

Acumatica webhook setup