Documentation

DupeBlocker 3 allows advanced users with development experience to further customize DupeBlocker to fit their specific business needs. Note:  Validity will not write custom code for customers nor will technical support be provided to troubleshoot ...

If you utilize the Salesforce standard Address Autocomplete functionality and enable the DupeBlocker wrapper on the New/Edit page of the Account object, you will need to enable a setting in DupeBlocker to ensure the functionality continues to work...

// Sample custom test data generation class.// For DupeBlocker to utilize your custom data generator in unit tests it MUST be named the same// as this class: DB_CustomTestDataGeneratorglobal class DB_CustomTestDataGenerator implements CRMfusionDBR...

// Sample unit tests for custom DB unit test data generation.@isTestprivate class DB_CustomTestDataGeneratorTests{    // Test Account data generation.    static testMethod void testAccountDataGeneration()    {        DB_CustomTestDataGenerator gen...

Warnings are primarily created in DupeBlocker when a potential duplicate has been detected for a particular scenario and the Match on Insert/Update Action is set to Report Duplicate in Scenario details.Warnings are also created when: A Lead to Co...

Warning Tasks Tasks can be created to alert either the current user, the scenario owner or both when warnings are generated.When a Yes option is selected, a pop-up will appear with a link to the task.  This is the standard task reminder pop-up opt...

Warning Tasks Tasks can be created to alert either the current user, the scenario owner or both when warnings are generated. When a Yes option is selected, a pop-up will appear with a link to the task.  This is the standard task reminder pop-up op...

Warnings should be reviewed on a regular basis to avoid high Salesforce storage usage and running the risk of exceeding APEX governor limits when inserting/updating records that trigger DupeBlocker scenarios. If the records are confirmed as dupli...

Scenarios define the matching criteria for detecting duplicates and what actions should be taken when duplicates are detected.  Multiple scenarios can be defined for the same object.  Best practice is to define a series of scenarios to detect dupl...

Scenario rules determine what fields will be used to identify matches, and how the fields will be matched. All fields that are included in the scenario rules must be populated and must match (based on the mapping type used) for a record to be iden...

Scenarios can be customized to affect only a subset of records, and/or only fire for specific groups of users.  This allows for different triggering actions, matching techniques, and/or notification strategies to accommodate specific business need...

An internal table of duplicate keys needs to be maintained for all Scenarios to function properly. When DupeBlocker is initially installed, keys will need to be built for all deployed scenarios This includes the default scenarios that ship with ...

Scenarios are created for each object that will be deduped.  The Scenario Details provide general information regarding the scenario, e.g. name, object type etc. and also specify how duplicates should be handled once detected.  Different matching ...

DupeBlocker is installed with default scenarios for Accounts, Contacts, Leads, Lead to Contact, and Lead to Account matching.  There is a Rigid and a Semi Rigid scenario for each.  These can be used as is, customized or deployed as desired. To rev...

The DupeBlocker Logs tab (available with version 3.10 and up) uses Salesforce Platform Events to record manual/auto merges and conversions as well as any DupeBlocker Exceptions errors (i.e. errors building keys, unable to lock row errors, auto-mer...

Note:  Auto-Convert WILL NOT work for Person Accounts. Lead to Contact and Lead to Account scenarios have an option to Auto Convert Lead when a match is found.  When a new Lead is inserted it can be automatically converted and merged into an exist...

When a new duplicate record is inserted it can be automatically merged into an existing record vs. blocking or reporting the duplicate. This option can be used with any object and any scenario.  Its primary purpose is to auto-merge records being e...

Since DupeBlocker will work with any single insert, it will trigger for Leads entered using the Web to Lead capability within Salesforce and will catch duplicate Leads as well as Lead to Contact and Lead to Account matches. Web to Lead scenarios c...

DupeBlocker - Sample Lightning Redirect Controllerpublic with sharing class CustomContactRedirectController {    /******************************************************************************/    /* If you're modifying this for use with an object...

DupeBlocker - Sample Redirect Controllerpublic with sharing class CustomContactRedirectController{    /******************************************************************************/    /* If you're modifying this for use with an object other than...

<apex:page showHeader="false" sidebar="false" controller="CustomContactRedirectController">    <style type="text/css">body,html,iframe {    height: 100%;    width: 100%}div.matchesDiv {    /*********************************************/    /* Set ...

Custom Lightning Redirect VisualForce Page<apex:page showHeader="false" sidebar="false" controller="CustomContactRedirectController">    <apex:pageBlock >        <apex:pageBlockSection columns="1">            <apex:outputPanel >                <ap...

QUESTION: I would like to customize the redirect text and/or add fields in the pop-up list that appears in the upper right when multiple matches are found. How can I accomplish this? ANSWER: This is accomplished with a custom Visualforce redirecti...

Now that DupeBlocker has been installed and configured, end users need to be notified of the changes that will be seen in Salesforce as the objects you implemented DupeBlocker for are inserted or updated. In an effort to facilitate user adoption o...

DupeBlocker will work with Person Accounts EXCEPT for the Auto-Convert feature. Additional configuration steps are required for DupeBlocker to function correctly with Person Accounts.  DupeBlocker Scenarios will also require additional customizati...

Dear Salesforce User, We have recently installed a new software package within Salesforce called DupeBlocker.  This new software will help in our efforts to avoid creating duplicates.  As a real time duplicate preventer/detector, DupeBlocker works...

Mapping types will determine how a field is evaluated as a match. Various options are available for matching similar field values (e.g. similar Account/Company names, street addresses, phone numbers, first names etc.).  Mapping Types Acronym Creat...

Potential duplicates can be merged/converted directly within the DupeBlocker application from a warning object. DupeBlocker uses the APEX merge/conversion calls to process Account, Contact and Lead merges and Lead to Contact/Account conversions.  ...

Note:  This sample is very basic and just displays the ids of duplicates found when saving a Lead from a custom VisualForce Page. VisualForce Page:  LeadCreation.page<apex:page standardController="Lead" extensions="LeadCreationController">    <ape...

 DupeBlocker Statistics are read-only and report on the effectiveness of a scenario.  Counts are incremented when Warnings are created and/or records are blocked or merged.  The last modified information on a scenario (who and date) will be update...