What are Duplicate Rules and Matching Rules? How to Invoke Duplicate and Matching Rules in Salesforce without performing DML operations?

-

 Definition:

1.       Duplicate rules are configurations that define the conditions under which a record is considered a duplicate. These rules are applied to standard and custom objects in Salesforce.

2.       Matching rules determine how Salesforce identifies duplicate records when new records are created or existing records are updated. They define which fields to compare and the criteria for matching.

3.       Duplicate rules use matching criteria to determine if a new or updated record matches existing records in the Salesforce organization. Matching criteria can include exact matching or more flexible fuzzy matching based on specific fields.

Please note that we can only invoke these while performing DML operations like Insert or Update.

Duplicate Rule:

It’s Corresponding Matching Rule:

The Standard Contact Matching Rule criteria:

 

Blocking or Alerting:

Duplicate rules can be configured to either block the creation or update of a record if a potential duplicate is detected or to allow the operation but generate an alert for users.


Order of Execution:

Duplicate rules are evaluated in the order specified by the Duplicate Rule Processing Order. Salesforce processes the rules one by one, starting from the top of the list.

If a record matches the criteria specified in a duplicate rule, the corresponding actions are taken (e.g., blocking the record creation, and generating an alert).

Once a duplicate rule is triggered and its actions are executed, the subsequent rules in the list are not processed.

Let’s see how it works out of the Box first.

Let’s say we already have a contact record with FirstName = Bharathwaj and LastName = Sridhar

When we are trying to create another Contact record with the same details we get an alert popover in the UI saying duplicate records found. Click on View Duplicates will allow the user to see Duplicate records in the UI. As we have enabled Allow create it still allows us to create the record.

                                                      But these popovers are only triggered on Record Pages. 

How can we trigger these duplicate rules in a Custom LWC component?

Step1. Collect necessary data from the LWC component and make a server call using wire or ConnectedCallback() and pass the necessary data to the Apex Controller.

Step2. Our Apex controller collects the data and invokes the Duplicate Rules for the Contact object as in this case we passing a list of contact records in the Datacloud.FindDuplicates.findDuplicates(conList); where conList is the list of contacts that are sent to the findDuplicates() method.




Step3. If you follow the above code, we can trigger the firing of Respective duplicate Rules based on the SObject type we pass in the findDuplicates() method. We can return the Duplicate records to client side and display potential Duplicates without performing any DML operations!

Happy Coding!






Comments

Post a Comment

Popular posts from this blog

Apex Best Practices

-
Image
Apex Best Practices: 1. All constants should have uppercase names, with logical sections of the name separated by  underscores. 2. Always check the returned values from Database.delete(), Database.emptyRecycleBin(),                    Database.insert(), Database.undelete(), Database.update() and Database.upsert() calls. If a list is passed to any of these methods, the call will return an array[] of results; the apex code must check all the return values in the returned array of results.  3. Classes that contain methods or variables defined with the webService keyword must be declared as global. 4. Declare instance variable as private or protected. 5. Declare only one variable per line of code. 6. Define meaningful numbers using clearly named constants (static final). 7. Do not instantiate any object before you actually need them. Specifically outside a try-catch block. 8. Each method name should have meaningful names start...
Read more

LWC Best Practices

-
1. Use the Lightning Data Service or cache data whenever possible 2. Before making a call to the server, make sure there's no other option to obtain the data 3. Consider passing data between components using attributes, events, or methods rather than retrieving the same data in different components 4. If multiple components on a given page retrieve the same data, consider creating a service component that has no UI elements and can query data once so that it can pass data on to other components. 5. Only SELECT the fields you need. 6. Set a LIMIT on the query, don't return huge numbers of rows at once 7. Implement pagination when queries may have large result sets. 8. Don't preload data that the user may never need 9. Put the least accessed components in a secondary tab that the user may not click. 10. Don't make a call to the server to filter or sort data you already have at the client side. JavaScript Arrays have built-in functions to do things like sort, filter, and f...
Read more