Duplicate Detection with Related Records

(0) Share

Report

Posted on by ABrandow

Is there a best practice (or even a practice) where I can have my duplicate rule ignore inactive related records?

For example, we have a custom entity for test scores that we have dupe rule set up for that is matching test scores to test scores with the matching field value of application. If we're using the application (a related entity) as our matching value, is there any way to have the rule recognize the related entity is not active, so therefore do not create a new lead when we import these custom test scores?

It doesn't make a difference if the 'Ignore Inactive Records' is checked or not since that's just reviewing if the test score is an inactive record. (I was hoping it would and tested it both checked and unchecked.)

I'd be open to a 3rd party solution if there is one!

All responses (2)

Answers (0)

ABrandow 10 on at

Like (0)

Report

RE: Duplicate Detection with Related Records

This is great! I'll give a shot- thank you!
Suggested answer

rthompson 1,530 on at

Like (1)

Report

RE: Duplicate Detection with Related Records

Hi ABrandow,

In order to achieve your goal you can remove the rule on the entity and handle checking for duplicates using c# code.

Please see the below link.

mylearnings26.wordpress.com/.../