Stand & Stands Fields
The booth-placement family on exhibitor mappings: Hall, Stand (single), and Stands (multiple). These fields interact — configure them together, not in isolation.
ExpoPlatform targets
|
Field |
ExpoPlatform target |
|---|---|
|
Hall |
The exhibitor's Hall |
|
Stand (single) |
The exhibitor's Stand, plus the Stands collection as a single-item list |
|
Stands (multiple) |
The exhibitor's Stands collection |
Behaviour
Hall is a pass-through that runs before Stand, so Stand can pick up the hall value.
Stand writes the booth identifier and also fills a single-item Stands collection, so downstream features that read the multi-stand collection see a value. The stand is assigned to the configured Hall, or to the DefaultHall fallback when no Hall is mapped.
Stands (multiple) iterates over an array of stand objects — each yields one stand entry with its own hall read from inside the object.
Stand vs Stands: important
Both Stand and Stands (multiple) write to the same Stands collection. When both are configured on one mapping:
-
The multi-stand variant runs after the single Stand
-
The multi-stand variant overwrites the collection that Stand produced
Configure only one of the two, unless you deliberately want the single Stand as a fallback that gets replaced when the multi-stand array has data.
Options
|
Option |
Applies to |
What it does |
Default |
|---|---|---|---|
|
DefaultHall |
Stand |
Fallback hall name used when no Hall field is mapped. |
|
|
HallValuePath |
Stands (multiple) |
Path inside each stand object that holds the hall name. Required. |
— |
|
StandValuePath |
Stands (multiple) |
Path inside each stand object that holds the stand identifier. Required. |
— |
Value handling
-
Stands (multiple) with an empty source array writes an empty collection (clearing the exhibitor's stands).
-
Stand and Hall are pass-through — absent values simply don't write.
Related
-
Exhibitor Fields Reference — the registry entries.