Salesforce Duplicate Management

I discovered we have thousands of these. Can they and their related Duplicate Record Item be deleted? I'm pretty sure it's because one of our managed packages has a custom dupe management process, and when that is used the single Duplicate Record Item in the Set is not auto-deleted.

Hello, 

I'm looking for a custom solution to identify duplicate records across Contacts and Leads in my organization. Although duplicate rules can match across objects, a duplicate job will only run for the object defined in the matching rule. I understand there are paid options to accomplish this at scale, but I'm curious if anyone has successfully implemented a custom solution to accomplish this. At this stage, I'm simply looking to identify the number of duplicates I have across both objects. Any help or guidance is much appreciated. 

Thank you, 

Will 

Concept is simple: Think of companies with multiple store locations (like Starbucks) – there are multiple locations in a single city, but these Accounts are not duplicates -- the account name is similar, but the store number is unique.

We want fuzzy match on account Name to assist with preventing duplicates on account creation.  However we want the  matching rule to not-make-a-match if the Store Number value is different.  (Store Number field on the account is unique)

We essentially want to be able to have the Matching rules IGNORE the fuzzy match on Account Name if the values in Store Number field are different, but not blank.  

Example:

Existing Account:  Name = "Freeman, Inc"  Number = "1234"

New Account 1:  Name = "Freeman, Inc"       Number = "5678" --> desired result: No Match

New Account 2:  Name = "Freeman"             Number = blank --> desired result:  Match

Is there a way to do this with the standard Matching/Duplicate rules in Salesforce that we are simply overlooking?

We use NPSP, currently there are 3 emails fields, Personal Email, Work Email, Alternate Email. When creating matching rules, we need to create matching rule for each email field separately. Ideally, when importing Contacts, Salesforce should be able to match the email in the import file across all the fields. I can create an apex trigger to block duplicate record creation based on email addresses across all the 3 fields. But I think this is an unnecessary thing to do. This can be easily done if Salesforce allows multiple fields from the Contact object to be mapped in the matching rule. Currently Salesforce allows the same object only once in a matching rule. 

If anyone experienced the same issue and if could add a comment to let me know how you have resolved the issue, that would be great.

Hi! We're struggling with duplicate management, specifically matching rules and different record types. Mainly in leads and person accounts. Wanted to ask if someone has had similar issues and how you solved them? 

E.g. We have 6 record types for leads and 4 record types for person accounts. They don't have anything to do with each other, so leads with different record types are not duplicates. However, we're not able to use record type as a criteria for matching rule, to my understanding. 

We're also not able to use 'Type' as a criteria as we have leads with different types, that 

are

 duplicates.  

We have solved this with a custom text field where we add a record type name with a RT before-save flow when lead or person account is created. We also use this cross-object, for leads & person accounts with the same record type. However, this is not working too well, the duplicates aren't always recognized when records are created. 

When completing a merge in Lightning, not all of the fields display as they do in Classic.  Is there a way to customize or add fields?  There is one specific custom field that does not display, but is important to us in determining which to keep.

We recently added a new duplicate rule to compare leads to contacts, and it is activated but in it is only running against newly created or edited records. It isn't an option in Duplicate Jobs because it is a cross object duplicate rule. Is it possible to force this rule to run in SFDC (without a 3rd party application)?