Adding Mappings to Subscriptions

You can add custom mappings to subscriptions to define the relationship between a message key and a target field. During this process, you can see all available keys that are included in the published message and add them to the subscription as required. We recommend that you create the associated publication before adding mappings to the subscription as this enables you to select existing keys.

You can add a custom mapping to a subscription that contains a unique combination of target field and target child type. If a managed mapping exists with the same information, the custom mapping overrides it.

Note:

We recommend that you do not create mappings for fields that are specified as a correlation field:

• To view the correlation field on a declarative subscription, click the target object link in the Description section.
• To view the correlation field for a custom child object mapping, click  next to the relevant mapping.

To add mappings to a subscription:

1. On the Registered Products tab, click the name of the product containing the subscription you want to customize.
2. Click the name of the subscription you want to edit in the Subscriptions related list.
3. In the Description section, do one of the following:
   • To add a header-level mapping to a single field or a related child object, click Add.
   • To add a child-level mapping to a single field or a related child object, click next to the appropriate relationship.
4. Complete the relevant steps to create a mapping to a specific field or a related child object:
   Create a Mapping to a Specific Field

   1. Select the target field from the Target drop-down list.
      
      Fields are labeled "Field" in the drop-down list.
      
      
   2. Select the key that identifies the source information. We recommend that you select keys from the list rather than entering them textually to ensure you specify a valid message key.
      
      
      Tip:

      When mapping keys to child fields, the source data is obtained from a source on the same level in the hierarchy, if present in the message. If no key exists at the same level, the information is mapped from the closest key above the source in the hierarchy. We recommend that you define unique keys to avoid confusion with similar information within the hierarchy.

   3. For lookup mappings to records that do not have unique names, specify a source resolution key and a target resolution field to create an advanced lookup mapping. For more information, see Creating Mappings to Lookups with Common Record Names.
   4. [Optional] Select a data transformation table to apply. For more information, see Data Transformation Tables. If you selected a data transformation table that requires input from two source keys, specify an additional key.
      Note:

      You cannot use data transformation tables for lookup mappings that specify a source resolution key or target resolution field.

   5. For child mappings only: Select a target child type or type in the name of a new target child type. If blank, the mapping is assigned the Default target child type. For more information about target child types, see Splitting Source Data into Multiple Target Records.
   Create a Child Object Mapping

   1. Select the target object that you want to create records for from the Target drop-down list.
      
      Child objects are labeled "Related List" in the drop-down list.
      
      
   2. Select the key that identifies the source information. We recommend that you select keys from the list rather than entering them textually to ensure you specify a valid message key.
   3. [Optional] To conditionally create child records based on specific information in the message, select a child filter key.
      
      The child filter key must be a message key from the relevant child relationship portion of the message. If no matching key is found in the child relationship portion of the message, no child records are created.
      
      Leave this field blank to always create records for this child relationship.
      
      
      Show More

      The filter key determines whether child records are created or updated. For records to be created or updated, the value in the message must evaluate to true. For example, if you select a filter key that relates to an Active checkbox on the source record, the target record will only be created or updated if the checkbox is selected.

      Data Type Examples

      Data Type	Example
      Checkbox, formula of type checkbox	Selected
      Text, including static text, picklist value, formula of type text	True true
      Number, currency	Any value greater than zero, for example: 1 0.5

   4. Select the action to take for child records:

      Child Record Action	Description
      Add Only	Adds new records and leaves existing ones. Duplicate records might be created.
      Update Correlating	Updates existing child records that match the records in the message. Existing child records that do not match are not updated. If you select this option, the Child Correlation Field and Child Correlation Key fields enable you to specify the criteria that determines whether a record in the message matches an existing one.
      Update Correlating and Delete	Updates existing child records that match the records in the message. Existing records that do not match are deleted. If you select this option, the Child Correlation Field and Child Correlation Key fields enable you to specify the criteria that determines whether a record in the message matches an existing one.
      Replace	Deletes all existing child records and creates new child records specified in the message.

5. Click Update to create the mapping or Update and Add New to add another mapping at the same level.
6. Repeat steps 3-5 to create additional mappings.
7. Click Save.