Exact OnlineSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Exact Online connection the step signs in with. |
| Division | Leave empty to use the administration the connection signed in to. |
| ResourceRequired | text |
| Record IDRequired | The record's GUID — a Get node hands you records[].ID. |
| Fields | The fields to change as JSON, sent as a change to one record. A failed update is not retried on its own, because a body that adds a line to a list would add it twice. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `exact-online`) |
division | text |
resource | text |
recordId | text |
data | any JSON |
Output
| Field | Type |
|---|---|
updated | boolean |
recordRecord (Exact answers 204 with no body on success, so this is null) | any |
Sample output, and the expression for each field
- recordnull
- updatedtrue
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"division": "",
"recordId": "<record id>",
"resource": "<resource>"
},
"label": "Update",
"type": "exact.update",
"version": 1
}