#Duplicate Management1 discussing

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?

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?

Hi,

Thank you,

Aruna

Hi Experts,

I am experimenting with the Web to Lead feature, see article:

https://help.salesforce.com/articleView?id=sf.setting_up_web-to-lead.htm&type=5

Thsi feature seems to automatically block duplicates.

If I try to add a duplicate, it will simply not create the lead an send me an error via mail.

I want to allow duplicates, and manage them by myself in the system, since many duplicates are expected for my case. 

 Can anyone share their experience with this?

Thank you in advance.

#Web-to-lead #Duplicate Management

Hi,

I need to create a Matching and Duplicate rule for the standard object " Location" but unfortunately this object is not listed.

Any ideas why or how can I accomplish this?

Thanks in advance

In NPSP I created matching rules for Classy based on contact emails. If the donor’s email  in Classy = HomeEamil or WorkEmail or AlternateEmail it would be considered a match.

This was easy since these fields resided on the Contact record. However, In EdCloud there is the Contact Point Email object. I am very curious to see how people are addressing matching rules that could accomplish the same type of matching rule given the fields are on a different object?

Any help would be appreciate!

#Duplicate Management #Education Cloud

Hello I'm hoping someone else has encountered this problem before. I am seeking input on our current approach to managing duplicate leads. Currently, when a lead returns, even after several years since their initial interaction, they are merged with their original lead entry. However, this method is posing challenges as our reporting and operations rely heavily on the Lead 'Create Date'. How are other customers handling leads that revisit?

Hello,

we have fuzzy duplicate rules which are fine, but in some cases they detect "false positives". With the component "potential duplicates" on the account record page the message is prompted, that there may be duplicates of this record.

So far, so good. But in case of a false positive duplicate detection we'd like to allow the user to turn off the duplicate warning for the affected accounts. We tried to delete the corresponding DuplicateRecordSet and DuplicateRecordItems. But this has no effect, so the LWC for potential duplicates seems to do an instant check of the hash values.

What would be a good practice to "switch off" dedicated duplicate warnings? And who is the consument of the DuplicateRecordSet and DuplicateRecordItems? Is there another duplicate warning which depends on these entries we could use instead?

Regards,

Stefan

#Duplicate Management