Country Field
Resolves the incoming value against ExpoPlatform's Countries catalogue. Offered in visitor mappings and in the owner-account part of exhibitor mappings.
Country Field anchors a small family of related fields: Nationality shares its resolution logic, and City and Region depend on its result.
ExpoPlatform target
The value lands on the account's Country field. Nationality writes to the account's Nationality field through the same resolution logic.
Behaviour
The incoming value is interpreted either as an ISO 3166-1 alpha-2 code (default) or as a country-name string, controlled by the Country Matching option. It's then resolved to ExpoPlatform's canonical Country. The resolved Country is what downstream features (filters, lists, dashboards) operate on.
On push-back scenarios, the process reverses to deliver an ISO code or name back to the source system.
City and Region ride on the result
When Country resolves, City and Region values are looked up against ExpoPlatform's catalogues scoped to that Country:
-
Existing entries are reused
-
Missing entries are created on the fly and linked to the Country (City is also linked to the resolved Region when one is available)
Options
|
Option |
What it does |
Default |
|---|---|---|
|
Country Matching |
How incoming values are interpreted: ISO 3166-1 alpha-2 code, or country-name string. Applies to Nationality the same way. |
ISO code |
Value handling
If Country cannot be resolved (unknown ISO code or unknown name), the record is still saved — without a country, and without its City and Region values. City and Region are dropped rather than stored without a country to scope them to.
Related
-
Visitor Fields Reference — the registry entries for Country, Nationality, City, and Region.