Entity Configuration

Enabling entities is essential for creating and managing Duplicate Matching Rules and Conditions for any entity.

Given below are the steps to enable Entity Configuration in DeDupeD:

This will open up ‘New Entity Configuration’ form, where we need to fill in the necessary details.
Select the required ‘Entity’ from the appearing drop-down menu.

Client-Side DeDupeD Settings

Detect duplicates that are developed on the client side. i.e., duplicate records created from the record form.

Find Duplicate on Field Change: Select whether to detect duplicates on a change in field value. By default, it is set to ‘Yes’.
Find Duplicates on Save: Select whether to detect duplicates upon saving the record. By default, it is set to ‘Yes’.
Notify Duplicates on Form: Select whether to notify users about the duplicates of the existing record as a form notification. By default, it is set to ‘Yes’.
Select Forms for Duplicate Detection: Select the entity forms on which you want to enable DeDupeD duplicate detection, e.g., AI for Sales, Customer Profile Cases, and Information.
Authorized User Roles to Ignore Duplicates: From the list of security roles visible in the drop down, you can select the ones you want to allow to ignore duplicates and save the record. Here, as an example, we will select the ‘System Administrator’ role. In the ‘Authorized User Roles to Ignore Duplicates’ field.
Authorized User Roles to Merge Duplicates: From the list of security roles visible in the drop down, you can select the ones you want to allow to merge duplicate records. Here, as an example, we will select the ‘System Administrator’ role. In the ‘Authorized User Roles to Merge Duplicates’ field.

To see the result of this configuration, click here.

Server-side DeDupeD Settings

Detect duplicates that are created on the server side. E.g., duplicate records created through workflows.

Prevent Duplicate On: You can select an event on which to prevent duplicates, i.e., on the creation of new records or updating existing records.

Impersonated Admin User: Suppose you want to find duplicates for records you don’t have access to. Then you can select the user on behalf of whom the duplicates should be retrieved in the impersonated admin field. For example, if you select the user with system admin role in the ‘Impersonated Admin User’ field, then you’ll be able to find duplicates on behalf of system admin.

Exclude User Roles from DeDupeD: With this feature, you can choose a security role to prevent users with that role from accessing DeDupeD in CRM. Once excluded, users won't be able to use any DeDupeD features for the configured entity. Here we have excluded the Basic User role and the Forecast Manager role.

• Merge Settings: Define criteria for master record to which duplicate records will be merged.

Master Deciding Rule: Define the selection of the master record for merging the duplicate/subordinate records based on any one of the following criteria:
- Latest Modified: If you set the ‘Master Deciding Rule’ as ‘Latest Modified’ then duplicate/subordinate records will be merged with latest modified record.
- Oldest Modified: If you set the ‘Master Deciding Rule’ as ‘Oldest Modified’ then duplicate/subordinate records will be merged with oldest modified record.
- Latest Created: If you set the ‘Master Deciding Rule’ as ‘Latest Created’ then duplicate/subordinate records will be merged with latest created record.
- Oldest Created: If you set the ‘Master Deciding Rule’ as ‘Oldest created’ then duplicate/subordinate records will be merged with the oldest created record.
- Most Field Values: If you set the ‘Master Deciding Rule’ as ‘Most Field Values’ then duplicate/subordinate records will be merged to the record with most field values filled.
- Most Activities: If you set the ‘Master Deciding Rule’ as ‘Most Activities’ then duplicate/subordinate records will be merged to record with the most activities.

Criteria Based: You can also set ‘Master Deciding Rule’ based on filter criteria or conditions (conditions defined in Fetch XML). For example, if you want to set ‘Master Deciding Rule’ as ‘Active Contact’ that contains a specific ‘Company Name’, then you can do so by entering a Fetch XML code for the same.