The AutoMerge Blog

Explore AutoMerge tips, best practices, and the latest news

Install the AutoMerge Solution

How to import the AutoMerge Managed Solution into your Dynamics CRM The AutoMerge Managed Solution has the components that need to be added to your CRM to facilitate the viewing and quickly (or automatically) merging your already-tagged duplicate sets.  This article explains how you install the latest AutoMerge Solution (zip file). You’ll need to perform these steps for each CRM Organizations you wish to analyze for duplicates. (Production, Sandbox/Dev, Sandbox/Test, etc…) 1. Download the latest AutoMerge Solution here: the .zip file locally. 2. Log into your CRM as a user with the built-in System Administrator security role. 3. On

Read More »
AutoMerge CRM Connection Verify

How to Create an Azure App (User) for AutoMerge Service Connection

Create an Azure App User allowing the AutoMerge service to connect to your CRM. Microsoft no longer allows services such as AutoMerge to connect to Dynamics CRM using named users.  Services don’t and cannot do any multi-factor-authentication and using named users require that extra security layer. Here is Microsoft’s announcement to that effect:   This article will show you how to set up an Azure App and then configure AutoMerge to use it.  High-Level Steps A – Azure Portal Active Directory – App Registration: Create Azure App Registration Add specific permissions to the App Create a Secret within the

Read More »
CRM Contact Form with am_automergemodifiedon highlighted

The usefulness of Dynamics CRM’s modifiedon field is limited. We can do better.

The usefulness of Dynamics CRM’s modifiedon field is limited. We can do better. The out-of-box modifiedon field tells you when the last time any change was made to a record. The CRM platform creates and manages the modifiedon field for all built-in and custom entities.   See below the modifiedon field shows 3/31/2021 @ 4:05pm: The problem with modifiedon is that any update to the record causes this date to be updated.  The platform tracks all fields’ changes whether they’re updated by an end-user, some plugin, workflow or integration processes etc…. Even if you update a field to a value that is

Read More »
AutoMerge Match Rules

Configuring Match Rules – Deep Dive

Deep Dive: Configuring Match Rules in the AutoMerge Management App The match rules within your Matching/Ranking Configuration record reference a particular entity (Lead/Account/Contact) and determine how the analysis engine finds duplicates in your CRM.  The default set of Match Rules created under each of your Matching/Ranking Configurations are suitable for typical CRM systems where the usual built-in fields from the Lead/Account/Contact entities are used. Fields containing data that uniquely identifies a person or a business such as firstname, lastname, company name, telephone, email, street address, etc… are key to setting up proper rules for your dataset. Let’s go over how

Read More »
Field Preservation Values On Loser Copy Via Workflow Rule

Configuring Complex Field Preservation to Run While AutoMerging Duplicate Sets

Configuring Complex Field-Preservation When AutoMerging a set of duplicates, our plugin will preserve populated fields from the loser records (Rank≥2) into UN-populated fields on the winner (Rank=1). It will do this for all fields contained in the comma-separated-list in the AutoMerge-Configuration record for that entity (Account, Contact or Lead). That works great when the Winner has no value, and the Loser does. Here’s a screenshot of the default field-preservation behavior: What happens when the Winner AND Loser records both have emailaddress1 populated with different values? During AutoMerge the loser’s emailaddress1 value would be lost and only available later from the Loser (disabled)

Read More »
Potential Duplicates with Editable Field Chooser Form screenshot

Potential Duplicates and Editable Field-Chooser Subgrid Web Resource

Potential Duplicates and Editable Field-Chooser Subgrid (Web Resource) A couple months back we announced a new web resource to show end-users the potential duplicates in a subgrid right on the form. That earler version depicts a read-only list of records that allows you to perform all the usual AutoMerge functions (Make-Winner, Ignore and AutoMerge). The main advantage of seeing potential duplicates in the form is that your end-users (the actual owners of the records) can be prompted to AutoMerge them as they discover them as opposed to having an IT/Analyst type person deal with them en masse from the list

Read More »