Skip to main content

Notifications

Customer experience | Sales, Customer Insights,...
Suggested answer

Duplicate Detection Rule 2 seperate fields

Posted on by 445

Hi,

Hoping you can help on this.

We use a Live Chat client (ProProfs) which generates Cases and Contacts within Dynamics 365.

A large number of our Contacts would have 2 email address,  Email Address 1 & Email Address 2.

However, if one of our existing Contacts uses the Live Chat system using their Email address 2 a new Contact is created each time, because only the email address 1 field is looked for when matching the Contact.

This had lead a huge amount of new and redundant contacts being created.

I have spoken with ProProfs and they say that its an issue within Dynamics.

My problem is that our developers tell me that its an issue with ProProfs.

Is there anything that can be done within Dynamics to resolve this? Is it possible to create a Duplicate detection rule to check 1 field against an another, or would I need to go down a different route?

Thanks as always

Ted

  • David Jennaway Profile Picture
    David Jennaway 14,063 on at
    RE: Duplicate Detection Rule 2 seperate fields

    Unfortunately the OOB duplicate detection rules won't work, as they cannot check different fields 

    You could go a bit further with the plugin logic. One approach that you could take is to have a plugin fire on the synchronous Post Operation stage of the create of a contact that:

    • Checks if there is a matching existing contact, based on the respective email fields
    • If there is a match, change the Id OutputParameter to be the contactid if the existing contact. This will mean that the calling code would think it has created a new contact, but actually receives the id of the existing contact
    • A new contact will still be created (you can't stop this, without the calling code getting an error), but the plugin could deactivate the new contact record, and/or set a flag field, and you could use a bulk deletion job to clear up the data. Or, you could create an addition asynchronous plugin step to delete the new record  
  • TedW Profile Picture
    TedW 445 on at
    RE: Duplicate Detection Rule 2 seperate fields

    Many thanks for your reply Miguel. I'm not a developer, but have spoken with one  of our team and he didnt think that your suggestion would work for us as it would likely cause issues for the case creation. He suspect it might mean that the cases don’t get created at all when that happens (an error would be thrown because the “Creator” field references a lookup to a contact that cannot be found)

    Thanks again

    Ted

  • Suggested answer
    RE: Duplicate Detection Rule 2 seperate fields

    Hi,

    you can always create a plugin that triggers on the pre create of the contact that will check if a contact with "email 1" or "email 2" already exists. If yes, stops, otherwise continues.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans