Data Controls Implementation Guide

10.3 HotFix 1
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3

Back Next

Duplicate Prevention

The goal of the Duplicate Prevention control is to bring the potential match capabilities currently available within the IDD to business users, who create master data in external source system within enterprise applications such as Salesforce.com, SAP, and Oracle ERP.

When a user creates a new record in the external source system, the component displays the potential matches and provides the user with the following options:

Navigate to the matched record, if it exists in source system.

Ability to create a new record in the source system, if it exists in Hub but does not have an XREF for the calling application.

This allows the business users to leverage the cleansed and correct data that may already exist in the MDM server and prevent the creation of duplicate data at the external source.

The control is not intended to address the overall integration or synchronization requirements between the external application and the Hub server. It is assumed that this is in place (batch and/or real-time).

This control is designed to be application agnostic. There must be a dedicated connector for the specific application that embeds the control.

The Duplicate Prevention control performs search for duplicates using search criteria passed in the control’s URL. If matched records are found, it displays them in a view similar to the Potential Matches IDD dialog, as shown:

Search criteria are passed to the Duplicate Prevention control as values of Hub match columns. To perform search for duplicates, control uses the searchMatch API with matchType=NONE. This matchType option is intended for searching, and therefore does not use a predefined match rule set; instead a dynamic rule set based on the match columns passed to the control is generated. Also, if base object is configured to use a Fuzzy match/search strategy, then the searchMatch API requires the value of the fuzzy match key to be specified.

If multiple matched records are found, then a user can navigate between them using the scrolling control to the left. The following buttons are available for each matched:

Open: The Open button is intended to be used to open matched record in the application embedding the control. This button is enabled if a matched record has an XREF record from the Source System that is configured as target Source System for the Duplicate Prevention control.
Import: The Import button is intended to create new record, in the application embedding the control, by using data of matched record found in Hub. This button is enabled if a matched record does not have an XREF record from the Source System configured as target Source System for the Duplicate Prevention control. If the import functionality is not needed, then control can be configured not to display the Import button.

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal