Due to spelling errors, nicknames, address change It is sometimes faster to create a contact record than to find and update an existing record:
It should be possible to use customer insight to choose duplicate detection fields and tables and provide a score back in Dynamics with potential duplicate to ease the merge of records:
Comments
Hi Pierre-Olivier,
Thank you for explaining the scenarios, however, a couple of points to note as well.
1. The match and merge scores etc, are more internal for CI processes and are not carried forward in the final Customer entity definition.
2. CI customer profiles are not merged with the native Contact entity or Account entity in Dataverse for a variety of reasons, and CI profiles and other output datasets are published as Virtual Entities in Dataverse.
Therefore, we will add this feedback to our backlog and will consider for your future enhancements.
Thank you!
Aditya Kuppa
Customer Insights team.
Category: Data Unification
Thank you Aditya :) !
Category: Data Unification
In Dynamics
We would like to see a Duplicate score (likely to be --> 100)
We would like to see the potential duplicate on CRM side (from a contact see the related duplicates)
We should understand what increased the Scorre (same adress in the past and the lastname sounds similar, of the firstname is a not exact but looks like a nickname Tim for Timotee... or sound similar mohammed/Muhmat)
We would like to be able to merge them (not only one by one but several at a time)
We would like a warning at creation -> your are 76% likely to create a duplicate due to (same lastname, same street , similar firstname)
Category: Data Unification
Sorry, missed to post some links to our documentation on these
1. Define deduplication: https://docs.microsoft.com/en-us/dynamics365/customer-insights/audience-insights/match-entities#define-deduplication-on-a-match-entity
2. Deduplication output as an entity: https://docs.microsoft.com/en-us/dynamics365/customer-insights/audience-insights/match-entities#deduplication-output-as-an-entity
Thank you!
Aditya Kuppa
Customer Insights team.
Category: Data Unification
Hi Pierre-Olivier,
Thank you for this feedback and we will add this to our future enhancements of the data unification process.
In the current data unification process, we have an option deduplicate/self-conflate with both deterministic as well as fuzzy rules and the output of the deduplication step is persisted as an entity for offline review as well.
Would like to hear from you more on how would you want to consume this output in Dynamics so please share your scenarios.
Thank you!
Aditya Kuppa
Customer Insights team
Category: Data Unification