Adding Custom Mappings from the FDN Mappings Component

In some circumstances, you can add custom mappings via the FDN Mappings component.

Depending on the configuration for the specific mapping scenario, when creating custom mappings, the following options might be restricted:

  • Creating custom mappings of specific types, such as static or advanced lookup
  • Overriding managed mappings with custom mappings
  • Creating or assigning target child types to child mappings
  • Disabling custom mappings
Note:

To view and manage mappings using this component, you need to be assigned the FDN Core - Mapping permission set.

To add mappings:

  1. Navigate to the Lightning page that displays the FDN Mappings component that contains the relevant mappings process.
  2. Complete one of the following steps:
    • Add a top-level mapping, click Add Mapping.
    • Add a mapping to an existing child relationship, click in the child relationship row and click Add Child Mapping.
  3. If required, specify a name that identifies the data. Mapping names are unique within their section of the mapping hierarchy. If a mapping already exists with the same name, a number is appended to the new mapping name when you save, for example, (1).
  4. Select a source type to define the type of data being published and complete the relevant steps.

    This option enables you to create a mapping from a field on the source object or a related object.

    Select the source field path.

    Tip:

    The following target types are appropriate for this source type:

    • Field
    • Transformed Data
    • Advanced Lookup for lookups that require additional input

    This option enables you to create a mapping where a fixed piece of data is sent.

    Specify a description of the fixed data you want to send and provide the exact data you want to send.

    Tip:

    The appropriate target type for this source type is Field.

    This option enables you to create a mapping between a related object on the source to a related object on the target.

    Specify the child object that will provide data for child source records.

    Tip:

    The appropriate target type for this source type is Child Relationship.

    This option enables you to create a mapping from the parent source object to a related object on the target. You can then add individual mappings to this relationship.

    Tip:

    The compatible target type for this source type is Child Relationship.

  5. Select an appropriate target type based on the source type you selected.

    This option enables you to create a mapping from a field on the source object or a related object.

    Select the field in which to store the data from the message.

    This option enables you to create a mapping from a field on the source object or a related object and apply a data transformation table to transform the target value.

    Select the field in which to store the data from the message and select a data transformation table to apply to the mapping. If you selected a data transformation table that requires input from two sources, specify an additional transformation source field.

    For more information, see Data Transformation Tables.

    In the FDN Mappings component, you can use the Advanced Lookup option for several purposes:

    This option enables you to create a mapping to a lookup where record names are not unique.

    To do this:

    1. Enter the name of the target lookup field you want to update.
    2. Enter the field that provides the additional identifier for the source object.
    3. Enter the additional identifier for the target record.

    For more information about advanced lookup mappings, see Creating Mappings to Lookups with Common Record Names.

    By default, advanced lookups match the source value to the value in the target's name field. If you want to create a lookup by matching the specified source value to a different custom field on the target, you can use the Advanced Lookup target type.

    To do this: 

    1. Enter the name of the target lookup field you want to update.
    2. Enter the field that provides the primary identifier for the target record. By default, the identifier is the Name field, but you can update this to be a different field on the target lookup.
    3. If the target identifier you specified does not contain a unique value, you can complete the following steps:
      1. Enter the field that provides the additional identifier for the source object.
      2. Enter the additional identifier for the target record.
        The combination of both source values must match the combined target values to identify a matching record for the target lookup.

    This option enables you to create a mapping between a related object on the source to a related object on the target:

    1. Specify the child object that will receive data and create child source records.
    2. [Optional] To conditionally create child records based on specific information in the message, select a child filter field. You can select any checkbox or formula field that exists on the source child relationship object.
      Leave this field blank to always create records for this child relationship.

      The filter field 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 field 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

      CheckboxSelected
      Formula of type checkboxSelected
    3. Select the action to take for child records:
      • Always Add - Adds new records for all the information in the message. Any existing records are unchanged. Duplicate records might be created.
      • Update Matching * - Updates existing child records that match the records in the message. Existing records that do not match are not updated.
      • Update Matching and Delete * - Updates existing child records that match the records in the message. Existing records that do not match are deleted.
      • Replace All - Deletes all existing child records and creates new child records specified in the message.

        • * If you select an Update option, you must also specify values for the Unique Identifier on Source and the Identifier Reference on Target fields.

        These fields enable you to specify the link between source and target records and determine whether a record in the message matches an existing one in the target.

        • The unique identifier field on source determines the field on the source that contains unique data that identifies the record, for example, the record ID or name.
        • The identifier reference on target determines the field on the target that saves that information to be compared by future messages.

        When you save the mapping, an additional mapping is created.

        You can optionally map this information to another field. However, we recommend that you do not create a mapping to the field that you specified as the identifier reference on the target.

    Note:

    You can only select targets that you have permission to edit.

  6. [For Child Mappings Only] Select a target child type or enter 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.
  7. Specify whether you want to save the mapping or save the mapping and create a new mapping. Typically, the button name is Save or Save & New. In some cases, components, the button names might have been overridden. For more information, see the Help relating to your specific use of the FDN Mappings component.