Options are available for customizing the application as a whole and/or customizing various mapping types to maximize finding duplicates. DupeBlocker comes with default settings and can be implemented without customization, however this tab must be selected after install to create a DupeBlocker license, and load the default scenarios and settings. Settings can be updated at any time.
Select the DupeBlocker Settings tab to begin customization or load default settings. The General Settings will load by default. Click a menu item on the left to modify that setting.
Options for customizing the application as a whole
1. General Account Information: Information regarding the license agreement and number of active scenario rules.
2. Export/Import Settings: Ability to export and re-import settings and scenarios
- Makes migrating scenarios from one Salesforce instance to another simple and easy. Simply export the scenarios and settings from one instance and re-import to the other instance, then rebuild all keys. No need to rebuild DupeBlocker from the ground up in production after testing in a sandbox. Also great for users that do not have full sandboxes (meta data only NO actual data copied) that currently lose all customizations to scenarios and settings when refreshing the sandbox.
- Settings exported from versions 3.8 and older are not compatible with versions 3.9 and newer. In order to import settings from an org running an older version to a 3.9 and higher org, the older org will first need to be upgraded to the newer release. Once that is done, the settings can be exported and imported into the newer org. More information can be found in the Validity Community Forum post: Error Importing Settings from a 3.8 org to a 3.9 org: Settings file is invalid
- The export file will contain:
- ALL Scenario info: including general settings, rules, filters and auto-merge and auto-convert settings
- ALL DupeBlocker Settings: including General Settings, Cleaned Account Name/First Name/State/Country Mappings and Web Lead Sources
- Important Notes When Importing Settings
- All Existing Settings/Scenarios will be deleted and re-populated with data in the chosen file
- All existing WARNINGS will be deleted
- Scenario Statistics will be set to 0 when the new scenarios are created
- Rebuild needed will be checked for all scenarios as keys will need to be built AFTER the import
- Use the "Rebuild All Keys" button within any scenario to delete any existing keys then build keys for the newly imported scenarios.
- Rebuild All Keys deletes ALL existing keys (i.e. those for any OLD scenarios that were deleted during the import process). If the keys are rebuilt individually per scenario (either the Rebuild Keys button from within a scenario or from a view), existing keys WILL NOT be deleted and will continue to use storage unnecessarily.
- Any enabled objects from the exported instance will need to be re-enabled
- Scenarios will be created for those objects but will not function until object(s) has been enabled
- All fields used in scenario rules/filters will need to be reviewed after the import as NO CHECKS are done to ensure that the fields exist in the "imported" instance
- ALL scenarios will be imported even those for objects that may not exist in the imported instance
- Scenarios for custom objects that do not exist will be ignored and should ideally be deleted after the import
- Note: Filter's based on Record Types, Users, User Profiles and/or Roles will use the Salesforce ID. When Exporting/Importing settings in the DupeBlocker Settings tab (i.e. Scenarios, Filters etc.) to different orgs INCLUDING from a sandbox to production or visa versa, these types of filters should be manually evaluated after the import to confirm they are correct (edit/save to confirm the correct ID's are selected). Typically this is NOT a problem as these objects are considered meta data and as such will have the same ID's in production vs. a sandbox even for developer sandboxes (i.e. not full). The problem arises when the object was added to the sandbox AFTER the sandbox was created/refreshed as that object WILL NOT exist in production and/or may have a different ID.
- Login to the instance where the data should be copied from and click Export Settings
- A file called "DupeBlocker Settings.json" will be created in Salesforce Documents in the DupeBlocker Folder
- The filename is NOT customizable
- There will also be an option to open or save the file, save the file locally to the PC
- A file called "DupeBlocker Settings.json" will be created in Salesforce Documents in the DupeBlocker Folder
- Login to the instance where the data should be copied to and click Import Settings
- Browse to where the .json file was saved on the PC
- Select the file
- Select Upload to upload the data
- Note: The background will be grayed out while the upload is performed. This may take a few minutes to complete.
3. Administrator Email: Specify the primary e-mail address for DupeBlocker exception/error notifications.
Starting in version 3.10, which now logs ALL exceptions to the DupeBlocker Logs tab, if this field is left blank emails WILL NOT be generated for exceptions. They will be logged in the DupeBlocker Logs tab.
4. Key Builder Type/Batch Size: Defaults to 500 for Original and 200 for Batch
Key Builder Type: Original or Batch Apex
- Original: Uses API calls to build keys but runs faster than batch
- Uses approximately 1 API call per 1800 records
- Need to keep the key building window OPEN until the build is complete
- Closing the window cancels the key building process
- Batch Apex: Does NOT use API calls, but runs slower than original
- Key building window CAN BE CLOSED and the job will run in the background
- An email will be sent to the user that initiated the rebuild when the key build is complete
- Batch key builder progress can be monitored from Setup -> Administration Setup -> Monitoring -> Apex Jobs
Note: The difference in speed between the 2 key building options will vary. For batch, the speed will be affected by API server load and how Salesforce prioritizes batches. For original, the speed will be affected by the chosen browser and if keys are being built for a single scenario or multiple scenarios. Original tends to run faster than batch.
Key Builder Batch Size
- Default batch sizes were chosen to increase key building performance and avoid possible errors
- It may be necessary to lower the batch size if governor limit warnings are received while building keys
- More information on building keys can be found HERE
5. Block Bypass Creates Warnings: When checked warnings will be created when bypassing a block
- Scenarios that allow blocks to be bypassed via the "bypass block" scenario option can have warnings created so that a DupeBlocker Administrator is aware that a block was detected
- If warnings SHOULD NOT be created when blocks are bypassed, uncheck this option.
6. Disable Warning Task Reminders: When checked turns off reminder pop-ups for DupeBlocker Warning Tasks
- By default reminders ARE set for DupeBlocker Warnings Tasks so that there is a real-time notification that a Duplicate Warning was created
7. Disable DupeBlocker: An alternative to undeploying all scenarios and/or uninstalling if needing to temporarily deactivate the application.
- When checked, disables ALL functionality including duplicate checking and building keys for newly inserted/updated records
- Can be used when doing major uploads (e.g. millions of records using bulk API) to speed up the upload process (no keys built) and avoid record locking errors
- Also helpful if errors are being triggered by DupeBlocker preventing some other process from functioning properly
- A message will be shown in the DupeBlocker Settings Tab and also when accessing a DupeBlocker Scenario to remind the user that the application is currently disabled
Note: All scenarios will be marked as needing a rebuild when this option is selected. Be sure to rebuild ALL Keys after re-enabling DupeBlocker. Keys cannot be built while the application is disabled. The following message will be displayed if key building is attempted:
8. Insert/Update Action Tracking Fields: Directly mark records with the action that was taken when the record was inserted or updated.
This was designed to allow customers to bypass records that were auto-merged or auto-converted from round robin style Lead assignment rules, but can be used for any special integrations that requires bypassing when a record is merged or converted, or noting when a record was flagged as a duplicate.
To implement this feature two custom text(10) fields need to be added to the object (i.e. added to Leads/Contacts/Accounts or any other non-standard object that has been enabled), and then the fields need to be referenced in DupeBlocker Settings.
1. Name the fields DupeBlocker Insert Action and DupeBlocker Update Action
- The API Name should be the same
2. In DupeBlocker General Settings - > Advanced Settings populate the Insert/Update Action Tracking Fields with these field names
3. When records are inserted/updated those fields will be populated with one of the following values:
- none: No action taken
- warn: The record was flagged as a duplicate and included in a DupeBlocker Warning
- The value warn will STAY in the record even once the records in the Warning are merged
- merge: The record was flagged as a duplicate and auto-merged with an existing record
- convert: The Lead was flagged as a duplicate and auto-converted into an existing Contact/Account
4. For auto-merge and auto-convert actions the field values can be checked to ensure they populated correctly by checking the recorded values in the merge/convert task on the master record
5. If using the auto-merge or auto-convert options for insert, may also want to update the automerge/convert settings to set these fields to ignore vs. the default of update if blank.
In order to allow DupeBlocker to detect duplicates for non-standard objects they must first be enabled.
Note: Users must have "Modify All Data" and "Author Apex" permissions checked on their Salesforce profile to enable objects as custom apex code is created when non standard objects are enabled.
- Not required for Accounts, Contact and Leads as those are enabled by default
- Non-standard objects include all other standard Salesforce objects (e.g. Opportunities, Assets etc.) and custom objects
1. Select Enable Objects
2. Highlight the object to be enabled
3. Click Enable in the lower right
- A pop-up will be displayed letting the user know that user unit tests will be run for the object
- There must be at least one record for the object in Salesforce, otherwise an error will be displayed
- Once enabled another pop-up will be shown, click OK
4. Enabled objects will show at the bottom of the screen
- Objects can be disabled at any time in the future
Scenarios can now be created for the enabled objects:
- Scenario Type will now show any enabled objects below the standard types
- --Non-Standard-- object list
- Simply select the desired object and build the scenario just like any other scenario
- Rules and Filters will show the fields from the enabled object
- All the same options will be available for non standard objects as for Accounts, Contacts, Leads
More information on Scenarios can be found HERE.
Cleaned Account Name Settings
Rules for matching similar Account/Company names when using the Cleaned Account Name mapping type (common punctuation to ignore or standardize, common suffixes and prefixes to ignore). We recommend that customers review these lists and customize as needed for better matching.
More information on the Cleaned Account Name mapping type can be found HERE
1. Select Cleaned Account Name Settings and one of the sub tabs
- Replacements: Matches supplied abbreviations or ignores a word or character
- Prefixes: Ignores supplied prefixes
- Suffixes: Ignores supplied suffixes
2. Click New Entry to customize
3. Enter desired values
- NOT case sensitive
First Name, State, and Country Mappings
These mappings are also used to customize specific mapping types and are edited in a similar fashion as the Cleaned Account Name Settings.
- First Name Mappings: Used with the FirstName mapping type to match a nickname to its full equivalent, e.g. Mike will match to Michael.
- State Mappings: Used with the State Match mapping type to match state abbreviation to its full name
- Supplied entries are for the United States and Canada
- New entries can be added for international state abbreviations
- Country Mappings: Used with the Country Match mapping type to match 2 digit, 3 digit, and full country names (uses ISO codes)
A search box is also provided to check if a specific value exists in the lists
Web Lead Sources
Specify the Lead Sources that are assigned to Web to Lead inserts. Leads inserted via Web to Lead WILL NOT block inserts/updates, but rather will always create warnings instead. This is done by checking the Lead Source field to see if the record contains any of the sources specified here.
The list is pre-populated with Lead Source values. New values can be added by clicking New Entry. Existing values can be removed by selecting the value from the list and clicking Del. This list should be customized to include the organization's specific Lead Sources allowed for Web to Lead inserts.
When entering Web Lead Sources an asterik can be used as a wild card, e.g:
- *appexchange* - to specify Lead Sources that contains the word appexchange
- web* - to specify Lead Sources that start with Web
Note: Since this list contains "web*" the other entries that start with "Web" are not needed. They are the default values so were left in this screenshot as an fyi.
More information on customizing DupeBlocker for Web to Lead can be found HERE