• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Disable Smart Matching EmailHashBase table population for Dataverse environments

April 7, 2021   Microsoft Dynamics CRM

For anyone that has been using Server-Side Synchronization and automatic email correlation, you may be familiar with the term Smart Matching. I won’t go into detail on what Smart Matching is, but you can take a look at this document HERE. Smart Matching is a legacy email correlation method from as far back as CRM 4.0. Now, there are newer methods of Email Correlation that use an Exchange item’s ConversationIndex to correlate that email to an existing thread. This does not require Smart Matching or Tracking Tokens. I cover this setting in more detail HERE.

You can disable Smart Matching, but even though you have Smart Matching disabled, by default, we still populate the EmailHashBase database table in the event anyone was not using Smart Matching and decided to in the future. This would allow Smart Matching email correlation to work on historical items. However, for those that never intend to use Smart Matching, this will continue populating this table, impacting storage consumption. Additionally, with the newer Email Correlation option, Smart Matching is not necessary for proper correlation.

What is this setting?

We created a new OrgDbOrgSetting, DisableSmartMatchingEmailHashCreation. Changing this setting to true, will stop population of the EmailHashBase table. However, it will not remove the data from this table. You will need to contact your dedicated Customer Engineer or Microsoft support to complete that process.

Important Note:

If you set DisableSmartMatchingEmailHashCreation to True or if the EmailHashBase table is cleaned out/truncated and you were to choose to enable Smart Matching in the future (not recommended), email correlation would only work on emails from that day forward. 

Verify you are not using Smart Matching

First, you will want to go to System Settings, in the Email tab, to double-check you are not configured for Smart Matching and that you have only Use correlation to track email conversations checked. Also make sure you check with any relevant team members to ensure there is no plans to enable Smart Matching. If not, you are good to proceed. 

6138.pastedimage1617630039686v1 Disable Smart Matching EmailHashBase table population for Dataverse environments

Change the setting

 

Once you have confirmed this, you can disable the Smart Matching feature and table population. Go to Settings| Solutions and open the OrganizationSettingsEditor solution. It will likely prompt you that you are not on the latest version and to download version 1.0.2103.1201. Please download and import this solution. If you do not yet have this solution installed, you can install it from here

Once imported and upgraded, open the solution and find the following two settings.

0552.pastedimage1617630065757v2 Disable Smart Matching EmailHashBase table population for Dataverse environments

Click Add for each of these and choose Yes

2627.pastedimage1617630085049v3 Disable Smart Matching EmailHashBase table population for Dataverse environments

Then click Edit for each of these and change to true and click Update

7343.pastedimage1617630101420v4 Disable Smart Matching EmailHashBase table population for Dataverse environments

If you have questions, please feel free to comment.

Thank you for reading!

Aaron Richards

Let’s block ads! (Why?)

Dynamics 365 Customer Engagement in the Field

Dataverse, Disable, EmailHashBase, Environments, matching, Population, Smart, table
  • Recent Posts

    • Accelerate Your Data Strategies and Investments to Stay Competitive in the Banking Sector
    • SQL Server Security – Fixed server and database roles
    • Teradata Named a Leader in Cloud Data Warehouse Evaluation by Independent Research Firm
    • Derivative of a norm
    • TODAY’S OPEN THREAD
  • Categories

  • Archives

    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited