Resolving matching issues for a quarantined entity

A common quarantine management task is resolving matching errors caused by match rules. You can resolve a matching error when either of the following is true:

• The entity matches one or more golden records that are already linked to an entity in the originating source system (a possible duplicate).
• The entity matches multiple golden records that are not yet linked to an entity in the originating source system.

Before you begin

Resolving matching issues is not available if:

• Your role doesn't have the Match Quarantine entitlement.
• The entity wasn't quarantined because of a matching error.
• The entity was quarantined as a possible duplicate, but no matching golden records remain. (An informational message appears in this case.)

To view masked values, you need one of:

• MDM - Privileged Data Steward role
• MDM - Administrator role
• MDM - Reveal Masked Data privilege
• MDM - Data Steward role (or MDM - Stewardshipprivilege) and the Reveal Masked Data Hub entitlement (Advanced Security feature)

Open the resolve matching issues wizard

1. Select Stewardship > Quarantine.
2. In the repository/domain list, select the domain to see the quarantine entry list.
3. Click the Quarantined Date for the quarantined entity to see its details.
4. In the ⚙ Actions menu, select Match, then click Next.

What happens next depends on why the entity was quarantined:

If the wizard shows...	It means...	Go to
Potential Duplicates screen	The entity is a possible duplicate of one or more golden records	Resolve a potential duplicate
Choose a Match screen	Multiple unlinked golden records are eligible matches	Choose a matching golden record

Resolve a potential duplicate

1. Use the arrow icons to step through each golden record the entity potentially duplicates, comparing fields side by side.
2. Choose one action:
   • Ignore potential duplicates and create a record — incorporate the entity as a new golden record anyway.
   • Merge selected entity fields into an existing record — navigate to the matching golden record and select Selectively merge fields into this record.
     • Selecting the ID field unlinks that golden record from its current source entity and links it to the quarantined entity instead.
     • You can select entire collections, but not individual collection items, and not fields whose values already match the golden record.
   • Reject this quarantined entity — reject it outright.
3. Click Next.
   • Selected merge fields? → Continue below to select which fields to merge.
   • Otherwise → skip ahead to Review and submit.

Select fields to merge

If you chose to selectively merge fields, select the checkbox for each entity field to merge into the golden record, then click Next.

If merging also triggers a choice between multiple eligible golden records, you'll land on the Choose a Match screen — refer to the next section.

Otherwise, continue to Review and submit.

Choose a matching golden record

1. Use the arrow icons to step through each eligible golden record, comparing fields side by side.
2. When you find the golden record to link to the source entity, select Choose.
3. Click Next.

Continue to Review and submit.

Review and submit

1. On the Matching Conflicts Resolved screen, review the summary of the pending resolution.
2. Click Submit. Depending on the path you took, the repository will:
   • Incorporate the entity as a new golden record, or
   • Update the golden record and send a Reject Contributed Entity request to the contributing source's channel, or
   • Send a Reject Contributed Entity request to the contributing source's channel, or
   • Create the link between the golden record and the source entity.

Next steps

note

The quarantine entry stays in the list — even after the entity is successfully incorporated — until you click Close or click elsewhere on the Quarantine page. If incorporation failed, a new quarantine entry appears for the entity.

Before closing the detail view, use Previous and Next to navigate to other entries and resolve them individually.