Skip to main content

Hi everyone,

I have a question regarding Duplicate Rules design in Salesforce.

In a current implementation, we are evaluating whether to configure Duplicate Rules to effectively consider all records in the database, bypassing record-level security (sharing rules), in order to detect duplicates globally (across all Accounts/Contacts and companies).

The idea would be to run duplicate detection across the full database (not limited by user visibility) 

 

My question is:

Is this considered a best practice in Salesforce architecture?

Specifically:

  •  Are Duplicate Rules expected to always respect sharing rules and user visibility? 
  •  Or is there any recommended pattern where global duplicate detection (system-level) is acceptable while still maintaining security in downstream processes? 
3 件の回答
  1. 7月5日 8:41

    @Lena Wong In my opinion yes, its a best practice. The reason is the data or information is hidden from user. The article also explains how to merge in this scneario.

0/9000