Custom Field
Writes one source value into a named ExpoPlatform custom field. Available in the field mapping picker for visitor and exhibitor mappings across integrations. On exhibitor mappings it writes to the owner account.
ExpoPlatform target
The value lands on the per-event participation record — meaning the same person can carry different custom answers in different events. The custom field name you configure is where the value is written.
Options
|
Option |
What it does |
Default |
|---|---|---|
|
Custom Field Name |
The ExpoPlatform custom field name to write to. Required. |
— |
What happens per sync
What gets written depends on what the source system delivers for that field:
|
Source value |
Result in ExpoPlatform |
|---|---|
|
A real value — including |
Written to the ExpoPlatform custom field, replacing any stored value |
|
A whitespace-only string (for example, |
Written as-is — values are not trimmed |
|
An empty string |
Nothing — the stored ExpoPlatform value is preserved |
|
Absent path or |
Nothing — the stored ExpoPlatform value is preserved |
Empty and absent are treated as "no value behind the source", not as an instruction to clear. This is deliberate.
Blanking a value in the source does not clear it in ExpoPlatform
A registrant clearing an answer in the source system leaves the previously imported value in ExpoPlatform untouched. Clearing an ExpoPlatform custom field cannot currently be done through the mapping — edit the value in ExpoPlatform directly if it needs to go.
This behaviour is generic and applies wherever the Custom Field type is used, on any integration's mapping.
Related
-
Batch Custom Field — the array variant that writes one custom field entry per source question object.