Go to 'Settings' and select 'Advanced Settings':
You will now arrive at the Advanced Settings screen where you will have a sub menu on the left hand side of the page:
This section is where you can configure which attribute will be used when linking duplicate records rather than merging them. This can be set for both the Account and Contact Entities. By default these are set to the ParentAccountID and ParentCustomerID.
Note: DQ for Dynamics will only display editable attributes.
After creating any session, record pairs are identified which are already marked as suppressed in previous sessions and assigned with different review status in the session result table. Suppression settings are used to show/hide the permanently suppressed records with the help of options below:
Please Note – The settings in this module will not be applicable for Temporarily Suppressed records. Temporarily Suppressed records will always be shown in a collapsed mode on the Group Review screen.
The Audit log sections allows users to perform two functions:
There are 3 options to choose from:
Only Winning Records Logging Example
Record Title | Attribute Name | Master Original Value | Value From Duplicate | Status | CreatedOn |
---|---|---|---|---|---|
Dupe No.1 | City | 3 River | Three River | Winner | 01-01-0000 |
Dupe No.1 | abc@Example.com | aba@Example.com | Winner | 01-01-0000 |
All Record Logging Example
Record Title | Attribute Name | Master Original Value | Value From Duplicate | Status | CreatedOn |
---|---|---|---|---|---|
Dupe No.1 | City | 3 River | Three River | Winner | 01-01-0000 |
Dupe No.2 | City | 3 River | Thri River | Loser | 01-01-0000 |
Dupe No.3 | City | 3 River | Three Rivers | Loser | 01-01-0000 |
Dupe No.1 | abc@Example.com | aba@Example.com | Winner | 01-01-0000 | |
Dupe No.2 | abc@Example.com | def@Example.com | Loser | 01-01-0000 | |
Dupe No.3 | abc@Example.com | ghi@Example.com | Loser | 01-01-0000 |
Select the user to be shown on the CRM Audit Logs:
Note: For a Guide on how to install the our Audit Log Functionality. Please see our Audit Log Guide
Memo Field Configuration Settings will be used to define the Manual Fill rules for the Memo Fields from Account, Contact and Leads entity. After clicking on ‘Memo Field Configuration’ under 'Custom Settings', you will navigate to the screen below:
Select Entity: Select the Entity from the drop-down to set the Memo field configuration.
Display Attributes By: You can toggle the list of attributes of the selected entity either by:
Entity Attributes: As per the entity selected, all the related attributes populate here. You can drag and drop the attributes from here to the Memo fields section. You can sort the attributes in ASC or DESC order.
Mouse hover on the 'Attribute Icon' you will be able to view the name of type of attribute.
If attributes are listed by ‘Display Name’, mouse hover on the Attribute Name you will able to see the ‘Schema Name’ for the respective attribute and vice-versa.
You can search the required Attribute/Rule Option from the list by using Keyword Search feature. Please note - if the attributes are listed by ‘Display Name’, you can search only by the keywords for ‘Display Name’ and not by the keywords for ‘Schema Name’ and vice-versa
Default Action: The rules dragged in this section are listed here with the following information:
This section is to decide on the status of a lead record during a cross entity dedupe. From this screen you can set the ‘Status Reason’ for records from the Account, Contact & Lead entities when records are deactivated/qualified/disqualified.
Adding a new Status Reason: You can add a new status reason by clicking on the plus sign in the top right hand corner.
after which you will get:
From this screen you will be able to define the status reason relating to a specific entity.
Single Entity
Cross Entity
NOTE: Custom Status Reasons can be added by editing the status reason picklist values.
The Across Entity Merge Approach settings give you the ability to choose which approach to take when dealing with matches, we have added the following options: For Lead to account merging we are providing two approaches:
1. Link to Account 2. Link to Account, Merge & Deactivate
For Lead to Contact merging we are providing four approaches:
1. Link to Contact 2. Link to Contact, Merge & Deactivate 3. Link to Contact & Account of the Contact 4. Link to Contact & Account of the Contact, Merge, Deactivate
To edit your chosen approach simply double click the row you would like to edit, then choose your desired approach. Lead to Account:
Lead to Contact:
This section is used to define the list of transforms under particular categories. After clicking on ‘Custom Transform Library Configuration’ under 'Advanced Settings', you will navigate to the screen below:
Categories: Display the list of all the default and user added Custom Transform Libraries in ASC order by default. You can edit the library by expanding the groups and altering the existing libraries, or creating new custom transform libraries.
Example - 'Mickey Mouse' will now transform to 'MM' when this category is selected in the match transformations (step 3).
In order to add new transformations or create a new custom transformation folder then follow the following steps:
New Transformation: Please click on the plus icon where you can select and existing folder and then add your transformation values.
New Transformation Group: Please click on the folder icon. you will receive a pop up where you can add a new transformation category.
NOTE: Please remember to save before exiting the page.
This is used to select the related entities used for post merge de-duplication. This is to prevent loading of entities which you do not wish to de-duplicate.
First, select the entity where you would like to search for related entities. Then select the 'Include for Post Merge Configuration for the relevant entities.
TBC
This section allows you to select whether you enable the ability for users to automatically merge identical record in the Account/Contact or Lead entity.
Please select the entity and then activate/deactivate the rules as relevant. By default these will be activated.