The AutoMerge Blog

Explore AutoMerge tips, best practices, and the latest news

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 »
AppSource AutoMerge Page Screenshot

Test Drive AutoMerge on AppSource

AutoMerge is available for a “Test Drive” on AppSource We have converted our AutoMerge listing to TEST DRIVE so anyone can try it out.  AppSource is Microsoft’s marketplace to help businesses find tailored solutions (apps) for their industry. AutoMerge – Microsoft Dynamics 365 CRM Duplicate Detector and Merger – App Login What is the AutoMerge “Test Drive?” AutoMerge “Test Drive” is a Dynamics 365 CE (CRM) environment. This environment contains sample Leads, Accounts, and Contacts that have been pre-analyzed for duplicates. How can AutoMerge help me? Any CRM user who’s frustrated with multiple copies of the same customer record can benefit from

Read More »
CRM Connection Verification Form

Multi-Factor Authentication and CRM Connections

Multi-Factor Authentication (MFA) and CRM Connections Having trouble connecting your CRM to AutoMerge? Maybe it’s multi-factor authentication… Consider this scenario: You have enabled MFA on your AzureAD tenant. The particular user you are using for AutoMerge to access your Dynamics CRM has MFA required. You attempt to enter your regular user & password combo into the CRM Connection Verify page and it fails. What are you to do next? CRM Connection Verify Since the AutoMerge service connects as a service, it cannot go through the Multi-Factor-Authentication step that we humans have to endure. Hence this error. The work-around is App Passwords.  App

Read More »

Copyright © 2020 AutoMerge