Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Customer 360
  3. Getting Started
  4. Adding Records
  5. Finding Records
  6. Editing Records
  7. Working with Drafts
  8. Participating in Review Processes
  9. Importing Data
  10. Resolving Duplicates
  11. Investigating Data Changes
  12. Investigating Hierarchies and Relationships
  13. Viewing the Relationship Graph

Resolving Duplicate Child Records within a Record

Resolving Duplicate Child Records within a Record

To look for duplicate child records within a single record, open the record in the
Matching Records
view. Do not select any other records.
  1. With the record open, select
    Matching Records
    from the View list.
    In the grid, the second column contains the selected record. In this scenario, ignore any similar records.
  2. In the
    Navigate
    tab, expand a node and select a child record from the record.
    The grid changes. The second column contains the selected child record, which is the target child record. The remaining columns contain the sibling child records, if any.
  3. If you see a sibling record that is a duplicate of the target child record, select the check box in the column header. You can select more than one child record.
    The
    Merge Preview
    column shows the result of merging the target child record with the duplicate child records. The merge request is saved in an internal change list.
  4. Repeat the process on the remaining child records. Optionally, you can perform the same process on descendant records.
  5. In the
    Navigate
    tab, click
    Overview
    to return to the parent record.
  6. Click
    Merge
    , and then confirm the merge.
    The merge process implements the manual merge requests on the sibling child records. Based on your user role, one of the following actions occurs:
    • If your user role permits you to merge records without a review, the merge process merges the child records. The merged child records are in the active state.
    • If your user role requires a review process, the merge process initiates the merge review workflow. The child records that participate in the merge remain in the active state, but the merge occurs only after the merge proposal is approved.