

However, such an approach puts you on the defensive since you always have to be on the lookout for new duplicates. If we stick with the contact importing example mentioned above, both Salesforce and those apps require the user to import the contacts first, and then it would run the duplicate check.

Many third-party duplicate checking apps are struggling with the inability to catch all dupes. Importing contacts from a spreadsheet and migrating contacts to Salesforce from a previous CRM are just two examples. Even though Salesforce can notify users that they are about to create a duplicate record and even block them from doing so, there are many other ways that duplicates can enter the system. There’s Nothing to Prevent the Duplicates from Coming Inĭuplicates are stealthy. Such constant rule creation and management is unreliable and drains your time and resources. For example, if you have Web-to-Lead enabled, some of the rules could be blocking the leads from coming in.

This is simply unsustainable! Think about how much time it will take your admins to create all of these rules and make sure they are working properly. Therefore, if your company relies solely on Salesforce for duplicate detection, you will have to keep creating new rules to identify each type of duplicate. The Salesforce admin identifies the loophole in the existing duplicate rules and creates a new rule to fix it. Imagine the following scenario: an employee identifies a duplicate record and asks the Salesforce admin why the existing rules did not detect it. The Issue with Creating More Rules for Managing Duplicates
DUPLICATE DETECTOR SALESFORCE INSTALL
Let’s take a closer look so you can determine if you need to install third-party apps to help eliminate, or at least greatly reduce, the problem. These limitations of Salesforce duplicate management mean that you will always be grappling with the spectre of duplicates. Each individual matching rule will be executed individually and once the process is complete, you will get a Duplicate Record Set.

