jigx-com Jigx Acumatica
Use this skill together with the generic jigx skill. Read the generic Jigx references
for screen, form, datasource, tab, media, and PDF patterns. Use this skill only for
Acumatica-specific integration rules.
Workflow
- Read
references/recipe-index.md. - Confirm whether the task is inbound lookup sync, local-first outbound sync, direct
submit, file upload, or retry/error handling. For any offline/batch create or
update, read
references/acumatica-sync.mdbefore designing tables or actions. - Confirm REST versus OData. Prefer REST when possible.
- Confirm required
$expandvalues before implementing lookups that need nested data. - Keep Acumatica config casing exact:
acumaticaURLandacumaticaOdataURL. - Use
accessTokenwith type/valueacuerp; do not hardcode access tokens. - Preserve local-first behavior unless the app explicitly uses direct submit.
Reference Map
references/recipe-index.md- when to read each Acumatica reference.references/acumatica-rest.md- REST functions, parameters, payloads, errors.references/acumatica-sync.md- local-first sync, Remote states, command queue, parent-child search/replace, retry.references/acumatica-lookups-expands.md- lookup sync, OData/REST differences,$expand, force sync, dropdown fields.references/acumatica-files-submit.md- file uploads, PDF attachments, service order submit patterns.
Guardrails
- Never hardcode Acumatica access tokens.
- Never change
acumaticaURLoracumaticaOdataURLcasing. - Never assume nested fields are present without
$expand. - Never send Jigx internal fields to Acumatica.
- Never create a separate same-entity queue table for local-first create/update unless
the business flow explicitly needs a different table. Use the entity's local table
plus
Remote: "new" | "dirty" | "remote"as the default. - Never lose failed commands. Use command queue retry or explicit error records.
- Never overwrite local IDs in child records without replacing queued references when the queue still contains temporary IDs.