How to make life more convenient: Duplicate Detection Status Exact Match
Posted Tuesday, September 29th, 2009
When you begin creating an new Duplicate Detection rule or continue altering an existing one, the common behavioral actions are to include First Name, Last Name, Company Name, etc. The basics. And from there, yes, you will be able to detect duplicates as long as the data related to the records are in fact exact matches.
Here comes the big question: once you deactivate a particular record, wouldn’t the record automatically be excluded from Duplicate Detection results? No. It wouldn’t. Yes, it is an Inactive record, but it will still be included unless you specifically state that you do not want Inactive records to be included in the results.
The rule is set up to do exactly what you tell it to do. It won’t read your mind and think about what would be the most efficient additions to the rule.
If you want to only search inside of active records for duplicates, you need to include an Exact Match line on the Status field. (Be sure to save and republish the rule after making any alterations.)
This way when you go through and merge any records you find that are in fact duplicates, they won’t be included again and again in the search results. This makes it much easier to quickly dwindle down the amount of records that appear in the Duplicate Detection results.
Hope this helps!
Tags: Creat* a Duplicate Detection Rule, Duplicate Detection Rules, Dynamics CRM 4.0 Duplicate Detection, Example Duplicate Detection Rules, Status Match
Posted in Data, Duplicate Detection, Dynamics CRM
Not yet using Dynamics CRM? I.B.I.S., Inc. gives you the Dynamics CRM options you want, and the business results you need.
Learn more about our Dynamics CRM solutions
I’ve tried setting up this rule in MSCRM4.0 but it doesn’t quite work the way you’ve described. I sincerely wish it did, it would solve all my problems!
When I set up a rule with multiple conditions (i.e. same email and same status)the rule doesn’t group the conditions to check the record meets ALL the conditions before detecting a duplicate. Instead the duplicate detection matches when a record meets ANY of the multiple conditions, so a record with an Active status triggers a potential duplicate match with every other Active record of the same type.
It’s a pity one can’t group conditions into AND or OR conditions the way you can with the Advanced Find feature in MSCRM.
Is there another setting in MSCRM where you can specify how the conditions should be handled?
I have the same problem. I want to group 3 or more fields with AND instead of the default OR condition.. I looked around, but for now no solution. So if someone can post some info, or help, I will be most grateful.
Thank you in advance.