20

There is currently NO warning that you are losing interactions when you remove contact duplicates after merging.

This is a big problem for deduplication as there is no way to save the interactions, all you can do is keep the target interactions.

Also, it would be very useful to merge interactions in both cases:

  • Same email field:
  • Contact A: emailaddress1:example1@example.com
  • Contact B: emailaddress1:example1@example.com
  • Different email fields:
  • Contact A: emailaddress1:example1@example.com
  • Contact B: emailaddress2:example1@example.com

The second case is useful for fixing misconfigured form submissions without losing interactions. Example: The contact sent a submission with the email generated by our company and not his primary email.

STATUS DETAILS
Needs Votes

Comments

N

On our website, we offer downloadable contact via a form. When a person fills out this form, Dynamics 365 does the following:

  • A lead is created
  • A contact is created


When this person is already a customer, he's also already a contact in Dynamics 365. Which means we have a double.

We then merge the two contacts, which gives you the option to select which information from which of the two contacts you want to keep in the remaining (active) contact.


After the merge, the insights and history of the remaining, active contact is lost. When this person filled out the form, he gave us (and Dynamics) permission to track his behaviour. We of course want to keep tracking this person from that moment. But the insights are lost if you merge this contact with the contact that was already created in Dynamics.


Can this issue get solved? Can the history be merged into the remaining contact or could this merging process (where you select which data you want to keep from which contact) give the option from which contact you want to keep the history?

Category: Analytics and Insights

N

At the moment the insights of merged contacts will not be merged. Only fields stored in Dataverse can be combined.


The issue occurs when you need the history stored in the insights, which lays in Azure Blob storage. These information is lost and not visible in the insights of the contact after the merge.


Customers often experience the need to comprehend previous sctions taken from the contact.


It would be great if there is a possibility to merge these information as well.

Category: Analytics and Insights

N

It's a logical request, in case of MERGE, we don't want to loose the passed timeline activity, none of both contacts

Category: Analytics and Insights

N

Hello,


We need this merge functionality to keep all our customer data consistent,

Without this functionality the merge is not complete, and we don't get a good customer view.

Category: Analytics and Insights