Mapping Single-Select And Multi-Select Fields

Mapping Select Fields is a great way to sync consistent information across your End Systems. To ensure these Fields are able to properly Sync, the Field Label for each available value needs to match in both Systems. You can learn more about the difference between Field Values and Field Labels by referencing our "What is a Field Values Versus a Field Label?" article.

Getting Started

The first step required to create a Field Mapping for any of your Select Fields is to identify the Fields you are going to include in the mapping from each System. You will see the warning indicator pictured below on the Mappings page within your Sync portal if there are any mismatched Field types:

 

 

Setting The Select Field Options

Once any Select Fields in your integration are identified you can implement matching value options to the corresponding Fields in both Systems. Formstack Sync uses an exact match for Select Field values so it is important to ensure that spelling and capitalization match exactly. 

Multi-Select Fields

The information above applies to mapping your Multi-Select Fields, but it is important to note that Multi-Select Fields will NOT map to a Single Select Field, even when only a single value has been Selected in that Multi-Select Field. 

Mapping Single-Select To A Text Field

Single-Select Fields can be included in Field Mappings with a Text Field, but this generally only works best when only mapping Select Field to the Text Field. If there are values entered into a Text Field that do not match the available values for the Select Field, the entire record will not sync.

Field Value vs. Internal ID

Formstack Sync uses the Field Label for systems with both an internal value and a label. This is consistent across all systems and is an important functionality to note for Fields that have particular Field value requirements. Some examples include county codes, stage or status, and persona among others.  

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.