Transformations > Deduplicate transformation > Deduplicate transformation configuration

Deduplicate transformation configuration

When you configure a Deduplicate transformation in a mapping, you first select the deduplicate asset that contains the logic to include in the transformation. Next, you map the appropriate incoming fields to the asset.
The deduplicate asset specifies the type of identity that the transformation searches for. The identity type determines the types of input field that you must connect to the transformation. For more information about the fields that the Deduplicate transformation expects, consult the Data Quality user who configured the asset.
To configure the transformation, complete the following tasks:
    1. Connect the Deduplicate transformation to a Source transformation or other upstream object.
    2. On the Deduplicate tab, select the deduplicate asset that you want to include in the transformation.
    The following image shows the options that you use to select the deduplicate asset:
    The image shows the Deduplicate tab of the transformation. The tab properties include a Select button that you can use to add a deduplicate asset to the transformation.
    3. On the Incoming Fields tab, verify the fields that enter the transformation from upstream objects.
    By default, the transformation inherits all incoming fields from any connected upstream object in the mapping. You can define a field rule to limit or rename the incoming fields.
    4. On the Field Mapping tab, connect one or more incoming fields to the deduplicate asset.
    The fields that you map must include data that can describe an identity of the type that the asset specifies. The input fields must also include a field that can act as a group key during duplicate analysis.
    The tab lists the fields from upstream objects in the Incoming Fields section and lists the fields that the asset specifies in the Target Fields section.
    The incoming field names might reflect the names of the target fields in the transformation. If so, you can use the Automap options to connect the fields.
    5. Verify the output field properties on the Output Fields tab.
    The output fields include several metadata fields that contain important information about the results of the duplication and consolidation process. For more information about the metadata fields, see Metadata fields on the Deduplicate transformation.
    6. You can optionally rename the Deduplicate transformation and add a description on the General tab. You can also update the tracing level for the transformation on the Advanced tab. The default tracing level is Normal.
Example 2. Synchronizing data quality assets
If you update an asset in Data Quality after you add it to a transformation, you may need to synchronize the asset version in the transformation with the latest version.
To synchronize the asset versions, open the transformation in the mapping and select the transformation name in the properties panel. For example, in a Cleanse transformation select Cleanse in the properties panel. If synchronization is necessary, Data Integration displays a message that prompts you to synchronize the assets.
When you synchronize the asset versions, Data Integration may prompt you to propagate the field attributes of the current asset to other assets in the mapping. Data Integration may display the prompt if the current asset originates in an earlier version of Data Quality.
You select the assets to which to propagate the field attributes. You can select multiple assets and propagate the attributes in a single operation.
Note: Field propagation occurs by default for assets that you create in the current version of Data Quality.