AutoMerge Errors and Troubleshooting Reference Guide

Error: Two Minute Plug-In Timeout

Error: Two Minute Plug-In Timeout After you analyze/tag and validate your duplicate Leads/Contacts/Accounts in your CRM, you may run into the timeout error. 2 minute plug-in timeout error What’s causing this? Microsoft imposes the 2 minute plug-in timeout to make sure ISV code behaves nicely in a CRM deployment that may be shared with 100s of customers. What happens when I click the “AutoMerge” button? When you click the “AutoMerge” button, three things happen: For each field listed in the “Field Preservation List AM-Configuration” record:  If a field is empty (null) on the winner record (the winner holding a rank of

Error: ‘An Error Occured!’ Pop-Up When AutoMerging Multiple Duplicate Sets from List View

Error: ‘An Error Occured!’ Pop-Up When AutoMerging Multiple Duplicate Sets from List View After you have analyzed/tagged and visually validated your duplicate Leads/Contacts/Accounts in your CRM, you want to quickly AutoMerge multiple sets at once.  You open the “AM Dupes (^)” view, select records from multiple duplicate sets and click the “AutoMerge” button. Then, BAM. You get this very unhelpful error: An Error Occured Screenshot This pop-up may occur over and over as it works through all the duplicate sets you selected. This means you may have to click “OK” several times before you get control back from the browser.

Error: ‘Contact’ Entity Doesn’t Contain Attribute with Name = “X”

Error: ‘Contact’ Entity Doesn’t Contain Attribute with Name = “X” While AutoMerging, you may run into this error if you’ve removed fields from the entity you are attempting to AutoMerge. Metadata Error Dialog while AutoMerging During the AutoMerge of a duplicate set, fields from the Losing record(s) are preserved to the Winning record if the field is null (empty) on the Winner and populated on the Loser. The list of fields to preserve is defined in an AutoMerge Configuration record within your CRM system. Go to “Advanced Find” and search for all active AutoMerge Configuration records. There will only be 15

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

Copyright © 2020 AutoMerge