Differences

This shows you the differences between two versions of the page.

--- admin_functionality:settings:postmergesettings [2019/03/08 11:52]
luke.swanton
+++ admin_functionality:settings:postmergesettings [2022/02/11 17:00]
conor.doyle
@@ Line 1: / Line 1: @@
-====== Post Merge Settings ======
+====== Post Merge Settings (Dynamics ONLY) ======
+  * When duplicate records are merged, their related entity records are re-linked to the surviving master; this can cause duplicates to be introduced
+  * Our optional “Post-Merge” Module avoids this challenge, optionally de-activating or deleting identical duplicate records, so you can rest assured that your data is trustworthy and fit for use:
+    * Be confident in your data integrity, as all linked data will be duplicate free after merging
+    * Save time by avoiding manually deduping related entity records
+    * Achieve higher levels of trust in the related data linked to your Golden Record
+**NOTE:** Please see [[admin_functionality:settings:custom_settings|Advanced Settings]] for information on how to activate the relevant entities for de-duplication.
 ----
-===== How to Access this feature =====
+===== How to access this feature =====
-To Access this feature please select the 'Post Merge Settings' option in the settings drop down menu.
-{{ :admin_functionality:settings:open_post_merge.jpg?nolink&600 |}}
+To access this feature please select the 'Post Merge Settings' option in the settings tab.
+{{ :admin_functionality:settings:post_merge_screen.png?800 |}}
 ----
 ===== How to use this feature =====
-**Select Entity:** Select the one of the following entity to apply the settings for-
+Before selecting the related entities dedupe, please go to [[admin_functionality:settings:custom_settings|Advanced Settings]] to configure the related entities you would like to display on this screen. Loading all related entities will reduce performance. Please only select the Account/Contact/Lead related entities utlised in the Post Merge Dedupe process.
+**Select Entity:** Select the one of the following entity to apply the settings for:
   * Account
   * Contact
@@ Line 18: / Line 31: @@
   * **Search Entities:** You will able to search the entities from the list using keyword search feature, by click the search icon.
-**Add Post Merge Settings:** To add the settings for the related entity, you will need to drag-and-drop the related entity from the left hand side onto the ‘Post Merge Configuration’ grid on the right hand side. You will now get a window pop-up (see screenshot below) where you can set the ‘Duplicate Detection’ and ‘Primary Record Detection’ settings.
+**Add Post Merge Settings:** To add the settings for the related entity, you will need to drag-and-drop the related entity from the left hand side onto the ‘Post Merge Configuration’ grid on the right hand side.
-{{ :admin_functionality:settings:configure_post_merge_setting.png?nolink&400 |}}
+{{ :admin_functionality:settings:post_merge_drag_and_drop.png?800 |}}
-**Post Duplicate Detection Action:** You will be provided with following 3 actions to select one from:
+----
+==== Post Duplicate Detection ====
-  * **None:** If selected, no duplicate detection process occur for the selected related entity and all the related entity records shall move to Master records as per default CRM behaviour as it is. Please note, you won’t able to set the ‘Attributes configuration for Duplicate Detection’ and ‘Additional Settings’ if ‘None’ option is selected.
+{{ :admin_functionality:settings:post_merge_config.png?600 |}}
-  * **Deactivate:** If selected, the related entity records which are found as duplicates as per settings shall be deactivated post base entity records merging.
+You have 3 actions to choose from:
-  * **Delete:** If selected, the related entity records which are found as duplicates as per settings shall be deleted post base entity records merging.
+  * **None:** If selected, there is no duplicate detection process for the selected related entity and all the related entity records shall move to Master records as per default CRM behaviour. Please note, you won’t able to set the ‘Attributes configuration for Duplicate Detection’ and ‘Additional Settings’ if the ‘None’ option is selected.
-**Attributes configuration for Duplicate Detection:** Select the attributes (by dragging and dropping to RHS from LHS) for duplicate records detection. If the all selected attributes values found exact same then the records shall be declared as duplicates.
+  * **Deactivate:** If selected, the related entity records which are found as duplicates shall be deactivated post base entity records merging.
-**Additional Settings:** You can set the following additional settings to pre-process the data before duplicate detection:
+  * **Delete:** If selected, the related entity records which are found as duplicates shall be deleted post base entity records merging.
+**Attributes configuration for Duplicate Detection:** Select the attributes (by dragging and dropping from the left to the right hand side) for duplicate records detection. If the selected attributes values are found to be the same, then the records shall be declared as duplicates.
+**Additional Settings:** You can apply the following additional settings to pre-process the data before duplicate detection:
   * Ignore Special Characters
   * Ignore Spaces
   * Ignore Numbers
   * Ignore Characters
+{{ :admin_functionality:settings:post_merge_additional_settings.png?600 |}}
+----
+==== Primary Record Detection ====
+{{ :admin_functionality:settings:post_merge_-_primary_record_detection.png?600 |}}
+**Primary Record Detection Attribute:** Select the attribute from the list which will help to detect the Primary Record. You can select the ‘None’ option if you don’t want to apply ‘Primary Record Detection Settings’.
+**Primary Record Defining Attribute:** This is an optional feature. You can select the attribute (of type ‘Option Set’) from this list if you want Primary Records per option. E.g. If you select the ‘Communication Type’ attribute for the related entity ‘Phone’, you will receive the primary record for each communication type against the Master record.
+**Best Primary Record Detection Rules:** You can set the rules in sequential manner for detection of primary record(s).
+  * **Master:** If selected, the primary record(s) from the Master will be the winner.
+  * **Modified On (Newest/Oldest):** If selected, the Newest/Oldest modified record will be declared as winner.
+  * **Created On (Newest/Oldest):** If selected, the Newest/Oldest created record will be declared as winner.
+----
+==== Edit Existing Settings ====
+There are two ways to select an 'Edit Existing Setting':
+  * Double click the desired setting
+  * Right click the desired setting and then select 'Edit'

DQ for Dynamics™/DQ for Workbooks Wiki

User Tools

Site Tools

Differences

Page Tools