Adapter Custom Parsing
Some adapters support the option of Custom Parsing, where you can define how to parse specific fields from the raw data fetched. You can parse the data into an already existing field, or create a new one.
This option can be found in the adapter's Advanced Configuration section.
When adapters fetch multiple asset types, there is a separate Custom Parsing section for each asset type, as demonstrated below in the CSV adapter:
Expand each asset type's Custom Parsing section to add fields. For each field, specify the following:
-
Field Title - Select a column title from the list. Note that you can also select nested fields of complex fields, for example:
Network Interfaces:Ips. -
Raw Path - The path to the field in the raw data, for example:
my_path|my_sub_path -
Type - Select a field type from the list: string, boolean, etc. Will be ignored for common fields.
-
Field Structure - Specify whether the field is a single value or a list field. Will be ignored for common fields.
Click + Add Field to add as many fields as you like, or x to delete the row.
Raw Path Examples
If your raw data is in DOT_DOT notation, like the following example:
"\"Computer\"DOTDOT\"OS\"DOTDOT\"NT Info\"DOTDOT\"Server\"": "Yes",
"\"Computer\"DOTDOT\"Owner\"DOTDOT\"Display Name\"": "Josh Caruso",
"\"Computer\"DOTDOT\"Owner\"DOTDOT\"Lit Hold By Owner\"": null,
"\"Computer\"DOTDOT\"Owner\"DOTDOT\"Lit Hold By State\"": null,
"\"Computer\"DOTDOT\"Owner\"DOTDOT\"User Account Name\"": null,
"\"Computer\"DOTDOT\"Status\"": null,
"\"Computer\"DOTDOT\"Type\"": "Virtual Server"
Then the data you enter in the Raw Path field should be in the following format:
custom_fields|"Computer"."Status"
custom_fields|"Computer"."Type"
custom_fields|"Computer"."OS"."NT Info"."Server"
This format applies to both CSV and JSON.
Updated about 11 hours ago
