Best Practice to prevent duplicate record in crm 365

(0) Share

Report

Posted on by Keysersozeey

195

Hi, I have a question, I want to prevent record in my entity to be duplicated actually, I already create a plugin that runs on pre-operation it's working but its buggy. Why its buggy? because when the record is created at the same time when I said the same time the difference between the creation of one record with another is only a matter of a millisecond. So when both are checking if the record with the same name is already created or not it will return false. I come with a solution to make my plugin runs on post-operation and make it asynchronous, but it will delete both records instead. Any suggestion for this? Thanks in advance

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Verified answer

Rawish Kumar 13,758 on at

Like (2)

Report
Copy link

Link copied!

Hello there,

For preventing duplicate record creation - you should be able to use alternate keys in dynamics crm.

have a look here : docs.microsoft.com/.../define-alternate-keys-entity

you can have upto 5 alternate keys for the entity and in each alternate key you can have multiple fields within.

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report
Copy link

Link copied!

In addition you can also register your plugin on pre-validation (Synchronous) and return exception.

Was this reply helpful? Yes No
Mansoor Sulaiman 4,330 on at

Like (0)

Report
Copy link

Link copied!

Is there any specific reason not to use OOB duplicate detection rules?

Mansoor

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (1)

Report
Copy link

Link copied!

Duplicate detection rules will warn you with duplicate records , but you can create and not prevent you to create.

Was this reply helpful? Yes No
Keysersozeey 195 on at

Like (0)

Report
Copy link

Link copied!

@Rawish Kumar

Hi,

Thanks for your answer i will look forward to it

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Soooo I have configured an Alternate key using only the name field (text) but the records in this particular entity are created by a workflow. The duplicates are still creating. My research is indicating that neither duplicate detection or alternate keys stop a workflow from creating records. Is this true? Is there anything else or any suggestions ANYONE can offer me? We are completely native.

Was this reply helpful? Yes No
Suggested answer

crm development 870 on at

Like (0)

Report
Copy link

Link copied!

Hi Merry, As suggested earlier, write a Plugin on pre create of record. Check duplicate record and throw an exception. This will prevent from duplicate creation.

Thanks,

Anand

Was this reply helpful? Yes No
Suggested answer

Rawish Kumar 13,758 on at

Like (1)

Report
Copy link

Link copied!

Hi Merry,

An alternate key is essentially created at the database level which signifies that from no matter where a record is getting created i.e manual, import, workflow, plugin , integration etc. the alternate key will be enforced.

When you created the alternate key - the job was successful? I am referring to this : passion4dynamics.com/.../alternate-key-creation-stuck-on-pending-status

Was this reply helpful? Yes No
Jag S 214 on at

Like (0)

Report
Copy link

Link copied!

Hi Keysersozeey,

Did you find a solution as I have a similar issue.

Thanks,

Jag

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

In my case there were three different criteria in the workflow and the workflow kept triggering on a different one of the three and created duplicates. I tried the alternate key as well as a duplicate detection rule and those did not prevent duplicates. I created a business rule that evaluated for the various combinations of the three criteria and then added a simple yes no field on The entity and used to that in the workflow. I was able to stop the duplicates because once the value is yes the workflow no longer triggered.

Was this reply helpful? Yes No