- 27 Mar 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Parsing an Event Field
- Updated on 27 Mar 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
You can configure an Event (including the triggering event) to automatically parse a string field into key-value pairs during Workflow execution.
Parsing Requirements:
- Only String type fields are supported for parsing.
- The field must contain the "magic word" AXONIUSPARSER (case-insensitive) followed by a valid single-level JSON object.
- Only single-level JSON objects are supported. Nested JSONs are not supported (although some may parse successfully).
- Ensure there are no spaces between the curly brackets and the JSON object.
**Example: **
AXONIUSPARSER {"key1": "value1", "key2": "value2"}
Parsing Failure:
If the field does not contain AXONIUSPARSER, parsing is skipped, and the Workflow continues. The Run History does not include information about parsing.
If the field contains AXONIUSPARSER and invalid JSON syntax, parsing fails, but the Workflow continues. The Run History indicates a parsing failure.
Parsed Data:
The Run History drawer lists the data of each Event that was executed in the Workflow, under Data. This includes all fields in the original schema and their values. When parsing is enabled for an Event field, the field name and all its parsed key-value pairs are also listed.
Parsed fields do not appear in the Syntax Helper. However, you can configure a Dynamic Value Statement in an Action with these parsed fields.
To parse an Event field
In the Workflow, click the Event you want to configure for parsing.
In the Event pane, toggle on Parse additional fields.
From the Select event field to parse JSON from dropdown, select the field to parse. Only string fields appear in the dropdown, as only they can be parsed.
For the Asset value changed Event, choose to parse the current Field Value or Previous Field Value.