Skip to main content

#Duplicate Rules1 diskutiert mit

I created and activatted the following new account "matching rule" based on the account's shipping address, not the billing address:

 

(Account: Name > FUZZY: COMPANY NAME MatchBlank = FALSE) AND 

(Account: ShippingStreet > FUZZY: STREET MatchBlank = FALSE) AND 

(Account: ShippingState > EXACT MatchBlank = FALSE)

 

However, when I updated the Account Duplicate Rule to this new Matching Rule, accounts that match this rule are not triggering the "duplicate warning"

 

What am I missing? Any help or insight would be greatly appreciaited!

Creating a New Duplicate Account Matching Rule

 

#Sales Cloud  #Salesforce Developer  #Data Management  #Automation #Duplicates #Duplicate Rules #Matching Rules

6 Antworten
  1. 17. Nov. 2023, 15:34

    @Courtney Pazdra - I tested this in a demo org and the logic fired as expected on edit and on save of new record attempt. When you say it's not firing, are you making any changes to the source records to fire the rules since standard dupe rules only fire on a change or save event.

     

    Again worth calling out though is that fuzzy match on street is going to be tricky since there are several components to the open text nature that could trigger the potential match. It may be worth parsing the street value into unique attributes for evaluation rather than as a whole.

     

    Another option would be to force the users to use the Google address input rather than manual entry so it's harder to enter bad data. 

     

    Let me know if anything changes or if you want to jump on a screenshare to experiment together.

0/9000

How would you...?

 

I have a spreadsheet containing contacts, leads, and people new to our ecosystem whom I need to add to a campaign.  On the spreadsheet there is no indication of who is a lead, contact or new.  There IS an email address for most people.  When I tried to bulk load, my leads hit some duplicate rules.  

 

If they exist, I want to still add the existing member to the campaign.  I do not want to create leads if a contact exists, and I want to create a lead if NONE exist.  

 

How would you tackle?  Is there a way I am not thinking of that I can take the spreadsheet and determine before loading who exists, and if so as what type of object record?

2 Kommentare
  1. 27. Jan., 18:50

    The dummy field workaround works but it's a lot of manual steps for what should be a simple matching operation. The bigger problem is that Salesforce treats matching as exact-or-fail. 

     

    I'd recommend using a semantic matching tool. Sharing the one I'm building:

    everyrow.io/merge if you'd like to test it out free the next time you run into this.  Upload your spreadsheet and your Salesforce export, and the tool returns a cleaned file ready for Dataloader with the IDs filled in. It understands that "Bob Smith, VP Sales at Acme" and "Robert Smith, Sales VP, Acme Corporation" are likely the same person. And then for ambiguous cases like two different people with the same name, it will flag these for review. 

0/9000

Would it be possible to setup duplicate rules that only match on Parent Accounts or Child Accounts? Many of our child accounts are similarly named to their parent and my fuzzy logic duplicate rules seem to cause a lot of false positives.

 

#Duplicate Criteria  #Duplicate Rules  #Data Management  #Sales Cloud

5 Antworten
  1. Tom Bassett (Vera Solutions) Forum Ambassador
    8. Juli 2021, 15:11

    Hello Alan,

     

    If you have a indicator on the Account Record you could use that for a Custom Matching Rule criteria. 

     

    For example only run this logic if Is Child Account is TRUE. 

     

    You could use a formula to determine this by looking at the Parent Account field. 

     

    Thanks Tom

0/9000

I'm not sure if there's a solution out there for this but it's worth a shot! I've got matching/duplicate rules set up for Accounts and Contacts. However, we have a duplicate problem largely because reps will sometimes abbreviate an account name to ABC instead of typing it all out. My matching rule isn't set to catch when that happens:

Account: PhoneEXACTMatchBlank = FALSE) OR (Account: NameFUZZY: COMPANY NAMEMatchBlank = FALSE) OR (Account: WebsiteEXACTMatchBlank = FALSE

Is there a way to help the rule catch these potential duplicates by their abbreviated account names? I ask because I noticed that Global Search will pull up accounts like this for me. If I type in the abbreviation it will also show me an account with the name spelled out.

I'm also struggling because if I'm creating a new account that only contains one word that matches a different account the rule won't catch it. Which is probably for the best - I don't want it to pull up a million possible duplicates because my new account has "the" in its name. But, if I have three duplicate accounts such as "Soup Cans," "Cans of Soup," and "Celery In Soup" I'd really like my alert to pop up if someone tries to create an account that is simply titled "Soup."

Sorry for the book! Any ideas?

15 Kommentare
0/9000

We implemented Exact match rules on email on contact name and on Account, which is all fine. But two weeks later we tried to deploy a change set and got a very nice surprise. those duplication rules are firing on the Apex tests and on top of that false positive as our testclasses are all with see all data = false so any test will be in need of provide a new set of test data which of course is done as best practise in an utility class, which now with those duplicate rules activated fails..

 

I have opened a case with support but it seems to be they have no clue what I am talking about, is this a general issue (works as designed) or something which came with Summer 16, unfortunately the event of switching to summer 16 and implement the rule came one week after each other and the last deployment was before both. so I am unsure which cause the false positive on " System Error" there is already a contact with that email[]"

 

If there is no ad hock solution from salesforce we will need to create fields on Leads/ Accounts and Contacts which will be populated by the testclass and be part of the matching rules, which in return means iterating through all inherited apex code to ensure the population of those fields.

 

At this stage we are not able to deploy any change set which contains code as the test classes in production are now failing , thanks to data .com  That much to the idea going back to out of the box, with 3rd party tools we never encountered that issue

 

Any Ideas are appreciated

1 Kommentar
  1. 15. Apr. 2025, 20:19

    Many years later, but just wanted to say that we have run into this multiple times in our own org and it appears to still be an issue. 

     

    We are using Test.isRunningTest() and limiting our queries to constrain the data to records we know won't have dupes, but this may not work in all scenarios.

0/9000

Hi,

 

We have already 60k+ Person Account in our Org.

 

I set up some duplicate rules to be able report on the duplicates in order to merge them.

 

When I open records separately from the UI, the records are flagged as duplicates. 

 

BUT I discvoered that Duplicate Record Sets are empty. No record has been created for the Duplicate Person Accounts.

 

Any exaplanation ?

 

Thanks

#Duplicate Management #Duplicate Rules #Matching Rule

4 Antworten
0/9000

Hi All, 

I am having some issues with my duplicate and matching rules.

I believe the matching rule that I am building to be quite basic it is performing a fuzzy match on the account name and an exact match on the phone number or email address. Both phone and email are also selected to match if blank.

 

(Account: NameFUZZY: COMPANY NAMEMatchBlank = FALSE) AND ((Account: PhoneEXACTMatchBlank = TRUE) OR (Account: Company_EmailEXACTMatchBlank = TRUE))

 

I have one example in my org where there are 4 accounts, all owned by the same account owner, all have roughly the same company name, give or take Ltd, Limited, Plc etc, 2 have a matching phone number and 2 have blank phone numbers and all 4 have blank email address.

 

When I am logged in as the account owner, the lighnting component tells me that there are potential duplicates but only shows the accounts with the phone numbers.

 

I can only assume this is user error on my part but I thought that selecting match on blanks would include these other accounts when offering potential duplicates.

Am i missing a selection somewhere or not executing this correctly?

 

any advice would be greatly appreciated.

many thanks

Laura

#Duplicates #Matching Rules #Duplicate Rules #Sales Cloud

1 Antwort
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    6. Nov. 2023, 13:40

    If you select Match Blank Fields for a field and that field is blank in both records being compared, the fields are considered matches. However, if you select Match Blank Fields for a field and that field is blank in only one of the records being compared, the fields aren’t considered matches.

    https://help.salesforce.com/s/articleView?id=sf.matching_rule_matching_criteria.htm&type=5
0/9000
I saw that our sandbox got upgraded to Spring '15 and I wanted to check out the cross-object matching/ duplicate rules but cannot find where I would do that? i can see the custom objects when creating a new matching rule but could not figure out how to do cross object. I thought maybe select "Lead" as the object and then in matching criteria it would show me contact fields as well but that's not it either.
3 Kommentare
0/9000

Matching rule is created and active. Duplicate Rule is created. But when I hit Activate, the screen reloads but nothing has changed. It's not marked Active, I get no error nor message of any kind. Nor has waiting 2

 

#Duplicate Rules #Matching Rule #Duplicate Management0 minutes or so accomplished anything.

9 Antworten
0/9000

Does anyone know why the duplicate rule name is not populating when viewing a duplicate record set record?  Screenshot below.  Thanks!

Duplicate Record Sets

#Duplicate Rules #Duplicate Record Sets #Duplicate Management

9 Antworten
  1. 21. Juni 2021, 14:24

    Hey, @Gustavo A. Seluja

    The Duplicate Rule Name is populated only for Duplicate Record Sets that result of a Duplicate Job you could trigger as an admin.

    For duplicate record sets created as a result of standard duplicate detection on create/edit of a record, this field remains empty. 

    Lora.

0/9000