Mapping Single-Select And Multi-Select Fields
Included in this article
- Getting Started
- Setting Select Field Options
- Multi-Select Fields
- Mapping A Single Select Field To A Text Field
Mapping select fields can be a great way to get consistent information to sync across your systems. This process generally takes more time to set up as field values need to be matching in both systems.
The first step to getting started is to understand what type of field you are mapping. This information is available in your individual systems and Bedrock will give a warning if there are mismatched field types:
Once select fields are identified you can create matching select options for both of your systems. Bedrock uses an exact match for select fields so it is important to ensure that spelling and capitalization match exactly. For most systems Bedrock can read the internal value and the label for select fields.
In the example above the fields, Option 1 and Option 2 will sync. However Option 3 is not matching and will prevent any records with this option selected from syncing.
Mapping and options work the same way with Multi-Select fields, but it is important to note that Multi-Select will NOT map to a single select field. Multi-Select must be mapped to another Multi-Select field.
Single-Select fields can be synced between a text field, but it works best from the select field to the text field. If there are values entered into a text field that does not match the select field the entire record will not sync.
Field Value vs. Internal ID
Bedrock Data uses the field label for systems with both an internal value and a label. This is now consistent across all systems. This may be an important functionality to note for fields that have particular field value requirements. Some examples are county codes, stage or status, persona, ect...