Working with Duplicate Matching Rules

Import Rx provides you with two options to prevent duplicate records

  1. Import Rx Duplicate Rules (custom build de-dupe prevention solution within the Import Rx product)
  2. Salesforce Duplicate Rules (utilize Salesforce platform features to prevent de-dupe)


Import Rx Duplicate Rules

Note:
Using the Import Rx Duplicate Rules option, you can manage your duplicate rules at the Data Source level. We recommend this option if your data source contains fields for duplicate matching that may not apply to all records within your Org - such as a specific source ID, like the Common Application ID. The Import Rx Duplicate Rules provide the most flexibility for each Data Source, and we recommend this as the default option.

The dialog pictured below pops up when you click the “Duplicate Matching Rules” button in the top right corner of each object mapping section. By default there will be several rows available in the dialog to fill out. Each row is numbered, and it is this number that must be referenced in the Filter Logic at the bottom.

The first column contains fields, with the options being dependent on which object you are adding the duplicate matching rule to. If a lookup field is chosen, the second column “Lookup Object Field” will populate with fields on that object that can be used. Choose an Operator Type to compare the value chosen in column 1 with the value chosen in column 5. Filter Type allows you to determine if this last value is a static value or a value from the Big Table (pictured below).

Once all criteria have been added, enter the row numbers into the Filter Logic box. This works the same way as standard Salesforce filter Logic. Use the words “AND” and “OR” to specify how the criteria should be evaluated.

Use the "Add Filter Logic" button to create additional rows of filter logic. Having more than one row of filter logic causes it to behave similarly to assignment rules. The rows are evaluated sequentially. Upon finding a match based on the criteria in a given row, subsequent rows are ignored. In Fig 2.20 below, Import Rx will first look for a match on Email, then it will look for a match on First Name AND Last Name. If a match on Email is found for the Big Table currently being processed, it will not look for a match on First Name AND Last Name.

To remove a row, click the "Trash" icon.

Similarly to the mapping screen, messages will appear if there are unsaved changes, or if changes have been successfully saved.

Errors will appear to guide you if any part of the criteria is configured incorrectly. For example, if a row is not referenced in the filter logic (pictured below).

Working with Salesforce Duplicate Rules

Note:
Using the Salesforce Duplicate Rules option, you can manage your duplicates on the Salesforce platform level. We recommend this option if your organization is using Salesforce duplicate rules. To check whether your organization has active Salesforce duplicate rules, navigate to Setup and type "Duplicate" in the Quick Find box as shown below. Learn more about Salesforce Duplicate Rules here.




The dialog pops up when you click the “Duplicate Matching Rules” button in the top right corner of each object mapping section.



You can select multiple Salesforce duplicate rules (if available) for an object to de-dupe the records in import process.