# Group data mapping

Group data mapping is a useful feature that enables the automatic mapping of fields based on matches between the field name and data pill name. This is especially helpful when there are a large number of fields that need to be mapped, such as in database application.

The feature allows a 1-to-1 mapping of fields in a recipe step from a selected data source.

# Activate the group mapping wizard

To start using the feature, expand the recipe step you want to map. You will notice that a 4th icon, the group data mapping icon appears to the right of your recipe step as shown below. Clicking on the icon activates the group mapping wizard.

expand step to be mapped Activate the wizard by clicking on the icon

Group data mapping is available on all recipe actions except the trigger.

# Selecting the field group and data source

The wizard shows you the fields and field groups that can be mapped on the left and the available data sources on the right. The available data sources is similar to the app data tree that can be seen when recipe building.

Field groups are fields that appear as nested fields in the recipe UI. They follow the object structure you have in your application. You may select the entire step's fields (including nested fields) or a specific field group. The example below shows the nested fields 'Bill to' and 'Ship to' (highlighted in orange).

field groups An example of fields and field groups within an action

After selecting the fields to be mapped, select the data source the pills should come from. The data sources available are from your Account Properties, the trigger and all recipe steps prior to the one chosen. Similar to field groups, you can choose to map from the output of an entire step, or a nested array within. In the example above, you can see nested data 'Files' in the Salesforce output (highlighted in blue).

After selecting the fields and data source, the wizard will display the matches and will highlight them in bold on both the left and right. It will also show the number of matching fields below the 'Next' button. Select it to continue.

# How data sources and fields are matched

In the current iteration, the matches between data sources and fields are based on the name/label and API name of both the field to be mapped and the data pills from the data source.

  • Matches are case-insensitive
  • Matches ignore underscores and spaces
  • All data types (string, integer, boolean, and so on) can be matched to each other, but arrays cannot be mapped to non-arrays
  • The pill label and API name will be matched to the field label or API name
  • The match has to be an exact match minus underscores, spaces, and case

# Examples

All examples below refer to the field and data pill labels.

Field Data pill Match? Explanation
Account name Account name Yes Exact match
ACCOUNT NAME account name Yes Case is ignored
account_name accountname Yes Underscores and spaces are ignored
Account_name accountname_c No accountname_c has an extra character 'c'

# Data mapping preview

The second screen in the wizard will show you the fields that have successfully matched with data pills of the same name and data type. Check that the mappings are indeed the ones you are looking for. Then, using the checkboxes on the left, select, or deselect all the fields you wish to map.

mapping preview Data mapping preview

Select the 'Apply mappings' button and the pills will be automatically mapped in the fields. You can edit any mappings in the recipe.