Batch Custom Field

The array variant of Custom Field: it iterates over an array of question/answer objects from the source system and writes one ExpoPlatform custom field entry per processed question. Offered in visitor mappings.

Batch Custom Field is what powers the custom-questions import flows on Aventri and Visit — see those integration pages for the specific setup.

ExpoPlatform target

One custom field entry is written per processed question, on the per-event participation record. As with Custom Field, custom-question values are stored per-event, not on the account itself.

Behaviour

For each entry in the source array, the field reads the question name and the answer value from configured paths inside the entry, then writes a custom field entry named after the question.

Options

Option	What it does	Default
Custom Field Name Path	Path inside each entry that holds the ExpoPlatform custom field name. Required.	—
Custom Field Answer Value Path	Path inside each entry that holds the answer value. Required.	—
Custom Field Answer Text Path	Optional. Path to a human-readable label, for sources where the answer value is an opaque ID.	empty
Custom Field Answers Path	Optional. Path used when the answer is itself an array (multi-select questions).	empty

Value handling

An empty source array is a no-op — nothing is written.
Entries that don't match the configured paths are silently skipped — the rest of the array still processes.

Custom Field — the single-value variant, including the empty-value preservation rules.