Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

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 fields on the deduplicate asset.
    The fields that you map must include data that can describe an identity of the type that the asset specifies. You must also map a GroupKey field that the transformation can use to create groups 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.
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. For more information about data quality asset synchronization, see Synchronizing data quality assets.

0 COMMENTS

We’d like to hear from you!