Sonoma Partners Microsoft CRM and Salesforce Blog

More Than One Way to Skin a Dupe

Today's blog post was written by Jeff Meister, Principal Consultant at Sonoma Partners.

Recently, a colleague of mine was looking for potential solutions for an issue his customer was facing within Dynamics 365. These types of questions are a favorite part of my job, as they showcase our ability to creatively problem solve, allows us to collaborate and discuss options as a team, and demonstrates the flexibility of the solutions we work with.

Typically, within any CRM platform, there is more than one way to solve a problem.

Picture1And based on your area of expertise, you might come at issues from many different angles. Below is a recap of the issue at hand, as well as the suggested solutions that surfaced from the team.

My Client is uploading Accounts to D365 using native imports. Upon import, 50 records are failing due to being flagged as duplicates. Is there a way to quickly find out which existing records are the duplicates?

Seems like a simple question, right? Unfortunately, there is no way to do this natively in D365, hence the ask for proposed solutions.

Here are the various responses from the different disciplines within Sonoma...

Data Integration Developer Response:

  1. Pull the error file from the D365 import.
  2. Export a list of all Account records.
  3. Create a PowerBI model to do the comparison.

Developer Response:

  1. Pull the error file from the D365 import.
  2. Export a list of Account Records.
  3. Bring both files into Excel.
  4. Execute a Vlookup to determine the overlap between the two files.

The Simpleton Response (my response):

  1. Run a duplicate detection on Account to ensure there are no existing dupes.
  2. Run the D365 import, leaving 'Allow Duplicates' set to Yes.
  3. Run data import (creating the 50 dupes).
  4. Run a Duplicate Detection job to identify your dupes and merge appropriately.

There is a long list of Pros and Cons with each of the above options, and depending on your situation (skillset, timeline, budget, resources, User skill-set, etc.), one will likely be more attractive than the rest. So remember, as you face common challenges within your deployment, think creatively, collaboratively and understand that there is more than one way to solve most problems.

Do you have a CRM problem that needs solving? Let us know.

Topics: Microsoft Dynamics 365