---
schema_version: "1"
id: c60512183c7841ed091a306c17520907e0d23743a3c61ed0783a6b66691079a7
title: Define Field and Attribute Mapping
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_define_field_and_attribute_mapping.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_define_field_and_attribute_mapping.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ce7717ef0ac1cf980c83edeea98f7b12f0eed665ec878a0e38a028789de31151
description: Define how Dynamic Revenue Orchestrator (DRO) maps fields and attribute data between products. DRO uses this mapping to copy or transform commercial order data to the data that fulfillment systems or processes require.
products:
  - Revenue Cloud
release: "264"
---
# Define Field and Attribute Mapping

Define how Dynamic Revenue Orchestrator (DRO) maps fields and attribute data between products. DRO uses this mapping to copy or transform commercial order data to the data that fulfillment systems or processes require.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d222868e67">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d222868e67 ">To define field and attribute
              mapping:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d222868e67 ">
              <p>Fulfillment Designer</p>
              <p>OR</p>
              <p style="margin-bottom:0;">DRO Admin User</p>
            </td>

          </tr>
        </tbody>
      </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)

Note Before you begin, make sure you have created decomposition rules. For more information on how to create decomposition rules, see [Define How a Product Decomposes](https://help.salesforce.com/s/articleView?id=ind.dro_define_how_a_product_decomposes.htm&release=264.0.0&type=5 "Use the decomposition workspace to set up rules that control how a commercial product or product classification breaks down into technical products. Define conditions and priorities for the decomposition rules. By default, all products decompose into fulfillment line items unless you specify an execution rule and that rule evaluates to false for a given sales transaction item.").

To create a mapping for fields and attributes, follow these instructions:

1. From the App Launcher, find and select **Dynamic Revenue Orchestrator**.
2. From the app navigation menu, select **Products**.
3. Click a product.
4. Click the **Decomposition** tab and select a decomposition rule.
5. In the side panel, click **More** and then click **Field & Attribute Mapping**.
6. Click **Create Mapping**.
7. Click a source attribute or tag, and then click the target attribute or tag that you want to map to.
    
    See the supported target data types for each source data type in [Data Type Compatibility for Field and Attribute Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_comptibility_for_field_and_attributes_mapping.htm&release=264.0.0&type=5 "When you map a source attribute or field to a target attribute or tag, Dynamic Revenue Orchestrator (DRO) validates that the source and target data types are compatible. If they aren't compatible, the mapping can't be created.").
8. If in-flight amendments are enabled for DRO, select a Rule Enforcement:
    1. To include amended or canceled in-flight orders, select **All Fulfillment Requests**.
    2. To exclude amended or canceled in-flight orders, select **Initial Fulfillment Request**.
9. For Mapping Type, select **As Is**, **List Mapping**, or **Expression Set Based Mapping**
    - As Is mapping copies the exact value from the source product to the target product.
    - For information about List Mapping, see [Configure List Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_configure_list_mapping.htm&release=264.0.0&type=5 "Use list mapping to set up pairs of source and destination values. For example, a list of cities that pair with post code values. When the source value is a city name, the target receives the post code of that city. Configure list mapping from the Fields & Attribute Mapping section of a decomposition rule.").
    - For information about Expression Set Based Mapping, see [Configure Expression Set Based Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_configure_es_mapping.htm&release=264.0.0&type=5 "Use expression sets to perform complex transformations on the source product's fields and attributes and use the output variables of the expression sets to enrich the target product's fields and attributes. For example, set delivery priority in the target product based on the order value and the delivery zipcode.").
10. Save your work.

A line is drawn between the two items to show the mapping. When the commercial product decomposes, the target product is enriched with data from the source of the mapped pair. When you map a source product tag to a target product tag that points to a reference field, the data enriches only if the two fields are compatible. If they don't match, the enrichment process fails, and the Decision Explainer Service (DES) records the error in a log. See the Explainability Action Logs section in [Submit Order Action](https://developer.salesforce.com/docs/atlas.en-us.revenue_lifecycle_management_dev_guide.meta/revenue_lifecycle_management_dev_guide/actions_obj_submit_order.htm) and [Action Logs](https://developer.salesforce.com/docs/atlas.en-us.industries_reference.meta/industries_reference/connect_resources_get_create_action_logs.htm).

![The Fields & Attributes pane showing a source tag mapped to a technical product tag.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_mapping_line.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)

Note Field and Attribute mapping relies on context definitions. If you wish to create custom mappings, you must extend and customize th predefined context definitions included with DRO. For more information, see [Context Definitions for Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.dro_context_definitions_for_dynamic_revenue_orchestrator.htm&release=264.0.0&type=5 "Dynamic Revenue Orchestrator (DRO) context definitions contain the information required to fulfill a sales transaction. A context definition includes the relationship between nodes and their structure, attributes, context tags, and mapping. Context mapping updates the nodes and attributes with the correct input data from Salesforce objects.").

- **[Data Type Compatibility for Field and Attribute Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_comptibility_for_field_and_attributes_mapping.htm&release=264.0.0&type=5)**  
    When you map a source attribute or field to a target attribute or tag, Dynamic Revenue Orchestrator (DRO) validates that the source and target data types are compatible. If they aren't compatible, the mapping can't be created.
- **[Configure List Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_configure_list_mapping.htm&release=264.0.0&type=5)**  
    Use list mapping to set up pairs of source and destination values. For example, a list of cities that pair with post code values. When the source value is a city name, the target receives the post code of that city. Configure list mapping from the Fields & Attribute Mapping section of a decomposition rule.
- **[Configure Expression Set Based Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_configure_es_mapping.htm&release=264.0.0&type=5)**  
    Use expression sets to perform complex transformations on the source product's fields and attributes and use the output variables of the expression sets to enrich the target product's fields and attributes. For example, set delivery priority in the target product based on the order value and the delivery zipcode.

#### See Also

- [Define How a Product Decomposes](https://help.salesforce.com/s/articleView?id=ind.dro_define_how_a_product_decomposes.htm&release=264.0.0&type=5 "Use the decomposition workspace to set up rules that control how a commercial product or product classification breaks down into technical products. Define conditions and priorities for the decomposition rules. By default, all products decompose into fulfillment line items unless you specify an execution rule and that rule evaluates to false for a given sales transaction item.")