This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
admin_functionality:settings_overview [2019/09/06 14:15] conor.doyle |
admin_functionality:settings_overview [2021/07/06 08:42] conor.doyle |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Overview of settings | + | ====== Overview of Settings |
===== Settings ===== | ===== Settings ===== | ||
- | The sections below define the main functionalities within the Perfect and Merge application. The following steps outline an overview of the sections. Select the links for more information. | + | The sections below define the main functionalities within the DQ for Dynamics/ |
+ | |||
+ | {{ : | ||
---- | ---- | ||
- | ===== Attribute | + | ===== Match Groups ===== |
- | The settings applied in this section will allow you to define the ‘Attribute | + | The settings applied in this section will allow you to define the ‘Match Groups’. These groups can then be populated with the relevant ' |
- | {{ : | + | {{ : |
- | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | + | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: |
---- | ---- | ||
- | ===== Attribute | + | ===== Match Group Transforms ===== |
This section will allow you to modify and standardise your data via predefined transforms. This data will then be utilised for matching purpose. | This section will allow you to modify and standardise your data via predefined transforms. This data will then be utilised for matching purpose. | ||
- | {{ : | + | {{ : |
- | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | + | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: |
---- | ---- | ||
- | ===== Master Record ===== | + | ===== Master Record |
This section will be used to identify the Master Record among a group of duplicates. The Master Record will be detected on the basis of rules defined within this section. You will use the Master Records Settings for the ‘Auto Promote’ process at group and session levels. | This section will be used to identify the Master Record among a group of duplicates. The Master Record will be detected on the basis of rules defined within this section. You will use the Master Records Settings for the ‘Auto Promote’ process at group and session levels. | ||
- | {{ : | + | {{ : |
For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | ||
Line 40: | Line 43: | ||
- To select the information that will be checked for exact matching at the time of Auto Merge process at group and session level. | - To select the information that will be checked for exact matching at the time of Auto Merge process at group and session level. | ||
- | {{ : | + | {{ : |
For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | For an in depth guide on how to use this feature, please visit the **[[admin_functionality: | ||
- | |||
- | ---- | ||
- | ===== Auto Exact & Merge Rules ===== | ||
- | |||
- | The Auto Exact and Merge function is used to match duplicate records which score as direct duplicates. Activating this function will allow you to remove all exact duplicates without a review process. | ||
- | |||
- | For an in depth guide on how to use this feature, please visit the | ||
- | **[[admin_functionality: | ||
---- | ---- | ||
===== Manage Users ===== | ===== Manage Users ===== | ||
- | This window displays the existing MS CRM users list in your organisation/ | + | This window displays the existing MS CRM users list in your organisation/ |
* User Name | * User Name | ||
Line 64: | Line 59: | ||
* Administrator (Active if role is assigned to the user): Admin will able to modify the role access details. | * Administrator (Active if role is assigned to the user): Admin will able to modify the role access details. | ||
* Reviewer (Active if role is assigned to the user): Admin will able to modify the role access details. | * Reviewer (Active if role is assigned to the user): Admin will able to modify the role access details. | ||
+ | |||
+ | {{ : | ||
For an in depth guide on how to use this feature, please visit the | For an in depth guide on how to use this feature, please visit the | ||
Line 69: | Line 66: | ||
---- | ---- | ||
- | ===== Primary Account | + | ===== CRM Connections |
- | This screen allows you to review your Perfect and Merge CRM account details. | + | This screen allows you to review your DQ for Dynamics/ |
- | {{ : | + | {{ : |
Displays following details to the user: | Displays following details to the user: | ||
Line 111: | Line 108: | ||
For an in depth guide on how to use this feature, please visit the | For an in depth guide on how to use this feature, please visit the | ||
- | **[[admin_functionality: | + | **[[admin_functionality: |
---- | ---- | ||
- | ===== Custom | + | ===== Advanced |
- | Custom | + | The Advanced |
- | {{ : | + | |
- | 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: | + | {{ :admin_functionality: |
- | * **Hide Permanently Suppressed Records:** If selected, the Permanently Suppressed records | + | From here you will be able to navigate |
- | * **Show Permanently Suppressed Records:** If selected, the Permanently Suppressed records will be shown in the Group Listing and Group Review Screen (in collapsed mode). | + | *Basic Settings |
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | *Custom Transform Library | ||
+ | *Related Entities | ||
+ | *Auto Exact & Merge Rules | ||
+ | *Refresh MetaData | ||
- | * **Conditionally Hide Permanently Suppressed Records:** If selected, the Permanently Suppressed records will not be shown for the Groups in the Group Review Screen if at least one duplicate is available to review with Master; otherwise Permanently suppressed records will be shown in the Review screen in collapsed mode. | + | For an in depth guide on how to use this feature, please visit **[[admin_functionality: |
- | + | ||
- | For an in depth guide on how to use this feature, please visit **[[admin_functionality: | + | |
---- | ---- | ||
- | ===== Master Record Rule DB Setup ===== | + | ===== Across Entity Mapping |
- | You will have the ability to run the Master Record Rule Data Base Setup. By doing so, the CRM instance fields will be retrieved. | + | This section allows you manually map Attributes between two entities. |
- | * It’s necessary that you should run the setup to get all the updated attributes from the CRM instance. | + | {{ : |
- | * you have to run the setup every time the fields get updated in the CRM. | + | For an in depth guide on how to use this feature, please visit **[[admin_functionality: |
- | + | ||
- | The Process to run the setup is as follows: | + | |
- | + | ||
- | Click on ' | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | Display the following popup after clicking on ' | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | If you Click ' | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | After successful completion of setup, you will have the following message displayed. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | For an in depth guide on how to use this feature, please visit **[[admin_functionality: | + | |
---- | ---- | ||
- | ===== Map Entities Setup ===== | + | ===== User Permissions |
- | This button with automatically go through and map attributes from entities that are similar. | + | There are two types of User' |
- | + | ||
- | {{ : | + | |
- | + | ||
- | E.G. Lead.Fullname would map to Account.name if there was no Fullname Attribute in Account. | + | |
- | + | ||
- | For an in depth guide on how to use this feature, please visit **[[admin_functionality: | + | |
- | + | ||
- | ---- | + | |
- | ===== Cross Entity Mapping ===== | + | |
- | + | ||
- | This button lets you manually map Attributes between | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | For an in depth guide on how to use this feature, please visit **[[admin_functionality:settings: | + | |
- | + | ||
- | ---- | + | |
- | ===== User Permissions ===== | + | |
- | There are two types of User's in the Perfect & Merge application: | ||
* Administrator ( full access) | * Administrator ( full access) | ||
* Reviewer (may only review duplicates) | * Reviewer (may only review duplicates) | ||
Line 187: | Line 150: | ||
Please refer to the **[[reviewer_functionality: | Please refer to the **[[reviewer_functionality: | ||
- | **Note:** Each Perfect & Merge user may have both the permissions assigned. | + | **Note:** Each DQ for Dynamics/ |
**Note:** One Admin only user is provisioned by DQ Global’s Customer Provisioning Portal. | **Note:** One Admin only user is provisioned by DQ Global’s Customer Provisioning Portal. |