Map Nested Attributes in the Mappings Tab

[CommunityMod_WM]

This article explains how to identify and map nested attributes in the Mappings tab. You will learn how to create Universal, Recipient-Specific, and static mappings. You will also learn how to manage multiple data sets, flatten nested attributes for easier maintenance, and validate the resulting target output.

Article Contents:

• What is a Nested Attribute?
• Why Map Nested Attributes?
• Before You Begin
• How to Map Nested Attributes
  • Create a Universal Nested Mapping
  • Create a Recipient-Specific Nested Mapping
• Apply a Static Value to a Nested Child
• Add Nested Children to the Source List
• Work with Multiple Data Sets
• Understand the Data Layer Rule
• Flatten a Nested Attribute
• Review and Test the Mapping
• Important Notes
• Related Resources

What is a Nested Attribute?

A nested attribute is a parent attribute that contains multiple child attributes. Container and complex attributes are considered nested attributes. Common examples include an allergen panel, country of origin, or Temperatures. 

 

In the Mappings tab, a nested icon appears beside the attribute name. Expand the parent attribute to review its child attributes, help text, expected formats, and requiredness before creating a mapping. 

Why Map Nested Attributes?

• Use nested mappings when a recipient requires structured data you already maintain as simple attributes.
• Use them to manage nested data through simpler source fields instead of a Container or Complex attribute Format. 

Before You Begin

• Confirm the required source attributes are included in a Source Data View.
• Identify whether the mapping should be Universal or Recipient Specific.
• Review the nested child attributes and note which are required by the target requirement set.
• Determine whether each child should receive a mapped source value or a static value.

Note: Nested mappings connect simple attributes to nested child attributes. Direct nested-to-nested mappings are not supported. 

How to Map Nested Attributes

Within the Mappings tab, you can identify a Nested Attribute by the “” icon. Expand the attribute by clicking the caret icon to review the available child attributes, help text, format, and required or optional status. Select a child attribute to view its details in the right-hand panel. Follow the steps below to Map to a Nested Mapping: 

Create a Universal Nested Mapping

A Universal mapping applies to every recipient requirement set that contains the mapped target attribute.

1. Expand the desired nested attribute & point and click Source to Target attribute.
2. Repeat these steps for each required child attribute.
3. Click Save Changes.  

Create a Recipient-Specific Nested Mapping

A Recipient-Specific mapping applies only to the selected recipient and overrides a Universal mapping for that recipient when both exist.

1. Select the recipient or requirement set at the top of the Target column.
2. Set the Mapping Mode to Recipient Specific.
3. Point and click Source to Target attribute (Repeat for each required child attribute).
4. Click Save Changes. 

Apply a Static Value to a Nested Child

Use a static value when the same value should populate the selected target child whenever the mapped source does not provide a value. For example, if product weight is always maintained in pounds, a static value can supply the unit while the numeric weight remains mapped.

1. Click the Caret icon and select the Target Child Nested Attribute.
2. In the right-hand panel, click Create a Mapping.
3. Select Map to a Static Value.
4. Enter or select the value.
5. Click Save Changes.

Add Nested Children to the Source List

If the source attribute is missing from the Source column, add it before creating the mapping.

1. Open Mapping Settings.
2. Select or edit the Source Data View that should contain the attribute.
3. Add the required simple attribute or nested child attribute to the Data View.
4. Return to the Mappings tab and confirm the attribute appears in the Source column.
   If an attribute already appears in the Target column and can be used as a source, select the applicable Data View, select the attribute, and use the available Make It Shared or Add to Source option. 

Work with Multiple Data Sets

A data set is one complete occurrence within a nested attribute. For example, an allergen type and its containment level form one set. A product containing eggs, milk, and wheat requires three sets so that each allergen is represented separately.

1. Select the nested mapping to open its details in the right-hand panel.
2. Choose the Multiple Sets option.
3. Add the number of sets required for the product data.
4. For each set, map the appropriate source attributes or assign static values to the required children.
5. Review each set for missing mappings or invalid values.
6. Click Save Changes. 

Understand the Data Layer Rule

Nested mapping output does not merge with values already stored in the nested attribute. After you map into a nested attribute, every child that should contain data in the resulting record must be represented by a source mapping or static value. You do not need to map every available child—only those required for the target and those you intend to populate.

Flatten a Nested Attribute

Flattening creates simple source copies of selected nested child attributes and automatically maps them back to the original nested structure. Use this option when users need a single set of nested data but prefer to maintain it through simple fields.

1. Select the nested attribute.
2. In the Attribute Details panel, click Flatten Nested Attribute.
3. Select the Data View to add “Flattened” attributes to.
4. Select the child attributes to flatten.
5. Click “Flatten” to Confirm. The system adds simple copies to the selected Data View and creates mappings back to the original nested children.
6. Review the generated source attributes and mappings and click Save Changes. 

Review and Test the Mapping

1. Open the completed nested mapping in the right-hand panel.
2. Resolve any Mapping Issues by connecting valid values or applying a supported transformation.
3. Review locale settings when the source and target use different locales.
4. Open the testing experience and enter representative source values.
5. Review the generated output and expand the detailed result to inspect each nested child value.
6. If the result is incomplete, confirm every intended child has a source mapping or static value.
7. Save the corrected mapping and test again. 

Important Notes

• Direct nested-to-nested mappings are not supported.
• Container and complex attributes are treated as nested attributes.
• Map or set a static value for every child that should appear in the generated nested record.
• Nutrition Panel attributes are specialized module attributes and cannot be mapped directly. When available, use the related container attribute that has a predefined relationship to the module.
• A Recipient-Specific mapping applies only to the selected recipient.
• Flattening is best suited to simpler maintenance scenarios that require one set of nested data.
• Always review Mapping Issues and test the output before relying on the mapping in production. 

Related Resources

• Exporting Data Quality Report
• Mappings User Guide
• Mappings Overview Workshop
• Mappings Course in Syndigo University
  1. Click on the “?” icon at the top right of your account
  2. Click Syndigo University (new users will enter first name, last name & email to register)
  3. Click the Catalog tab at the top
  4. Find the Mappings Course
  5. Click to Enroll or Start Now