Step 1 - Session Setup

Created by Dariusz Szczendzina, Modified on Tue, 21 May at 3:58 PM by Ben Gilbey

This page details what is required for completing 'Step 1' of creating match sessions. 

This is shown on the screen below:

1. Session: Enter a unique session name

2. Match Type: You will now have two options from the match type drop-down:


Single Entity

Dynamics Customers

Once the 'single entity' dropdown has been selected, you will now be shown some extra fields to complete:

1. Session Type: Select 'Standard' for all regular deduplication sessions. For information on other types, please see the 'Create and Link' section of the Wiki. (insert hyperlink)

2. Entity: This drop-down allows you to select from your available entities.

3. View/Type: This defines what type of data set you would like to be fed into the Match Engine, you will have 4 options to choose from:

  • All Records: If selected, the session considers all the records from the Entity for the session. By default, this option is selected.
  • Personal: This will feed a data set from the Entity, which is exclusive to the Dynamics CRM User creating the session. Results of session will be visible only to that User. 
  • System: This will feed a data set from the Entity which is a default 'System' view within Dynamics CRM. Results of session will be visible to all Members of the organisation that has permissions to view the shared view within CRM.
  • Shared: This will feed a data set from the Entity which has been 'Shared' with other Dynamics CRM Users. Results of session will be visible only to Users who the data set has been shared with.

View: This is where you select what data the session has access to (this is disabled if All Records is selected).

Workbooks Customers

Once the 'single entity' dropdown has been selected, you will now be shown some extra fields to complete:

1. Session Type: Select 'Standard' for all regular deduplication sessions. For information on other types, please see the 'Create and Link' section of the Wiki.

2. Entity: This drop-down allows you to select from the Organisation or People Entities.

3. Report Type: This defines who can view the session you create, you will have 2 options to choose from:

  • All Records: If selected, the session considers all the records from the entity for the session. By default, this option is selected.
  • Report: This will make the session only visible to you, but with the caveat that it must be created and placed under the 'DQ'report category.

Across Entity (Dynamics ONLY)

Across Entity Matching allows you to match between two entities. You will now be shown some extra fields to complete, this is displayed in the screen below:

Note: The source table will be the table in which you make records inactive.

1. Cross Match:

  • Across Entity - Compare Records from 2 entities against each other ( I.E Lead → Contact/Account).
  • Within Entity - Compare Records from 2 views within the same entity.

2. Source Entity: Select the relevant entity

3. Source View Type: You can now select one of the following view type:

  • All Records: If selected, DQ for Dynamics considers all the records from the entity. By default, this option is selected.
  • Personal: This will make the session only visible to you, but with the caveat that it can only access data from other personal views that you have created outside of DQ for Dynamics.
  • System: This will make the session visible to everyone and give access to System views created outside of DQ for Dynamics.
  • Shared: This will make the session available to any groups or teams the 365 User is part of.

4. Source View: this section allows you to select the data that this session has access to (this is disabled if 'All Records' is selected).

5. Target Entity (Across Entity Only): Select the relevant entity that you want to compare the source entity against.

6. Target View Type: You can select one of the following view types:

  • All Records: If selected, DQ for Dynamics considers all the records from the entity for the session. By default, this option is selected.
  • Personal: This will make the session only visible to you, but with the caveat that it can only access data from other personal views that you have created outside of DQ for Dynamics.
  • System: This will make the session visible to everyone and have access System views created outside of DQ for Dynamics.
  • Shared: This will make the session available to any groups or teams the 365 User is part of.

7. Target View: This is where you can select what data the session has access to (this is disabled if 'All Records' is selected).


Session Settings

These descriptions refer to the right hand side section of the 'Create Session - Step 1'

Master Record Based On: How will the Master record be chosen? Using rule based logic or score based logic. See the Master Record Settings Guide for more details.

Auto Fill Based On: How will the master record get Auto Filled? Using the rule based logic or the score based logic. See the Display and Auto Fill Guide for more details.

Run Auto Promote: This option will run the Auto Promote process as soon as the matching process has finished, this will then give you the best matches per your rules for you to review.

Match Contacts at the same Company/Organisation - Contact/People ENTITY ONLY:

  • Enabling this option will change the search to look for duplicates within each company
  • Disabling this option will change the search to look for duplicates across companies

Include Inactive Records from Dataset: This option is only applicable for the Account and Contact entities. By default, it is unselected which means the inactive records from Accounts or Contacts will not be included in the session. If selected, the inactive records from Accounts or Contacts are considered in the session.

Matching Language: Choose which language you would like the system to match in (see below).

Folder Name (Optional) : This option allows you to select whether you would like to group this session in a specified folder e.g. Contact Sessions, Account Sessions etc.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article