ebms_write
Creates, updates, or deletes EBMS records and reads back sent fields to verify writes, reporting mismatches, missing rows, and EBMS-added entries.
Instructions
Write to EBMS: POST creates a record (documents take their lines nested as Details), PATCH updates one by quoted AUTOID (lines via a Details@delta array), DELETE removes one. Refused for a company that is not configured (or not the sandbox, while testing), and refused if the body carries PROCESS anywhere, a POST's EXTERNALID already exists (orders, POs, batches, tasks, customers, vendors, products, workers), or a vendor (APVENDOR) POST has no ID. A 2xx is not proof — EBMS silently ignores unknown @ids and unwritable fields — so the server reads back the fields you sent and returns a verification: ok, mismatches (sent vs stored), problems (a row that never appeared or was not removed), notes (rows EBMS added itself) and the stored rows. Treat ok:false as a partly failed write and tell the user. If the result says uncertain, read back before resending — a resent create or add duplicates; a create resent by EXTERNALID is refused until a read finds it or confirms it is absent.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON body for POST and PATCH. Omit for DELETE. | |
| path | Yes | Required. ARINV for a POST; ARINV('<AUTOID>') for PATCH or DELETE. | |
| method | Yes | ||
| verify | No | Default true: after the write the server reads back exactly the fields you sent and reports each mismatch. Set false only for a write whose result you will read yourself. | |
| company | Yes | Company, by ID or name as ebms_companies lists them. Required on every write. | |
| readBack | No |