Salesforce Editions Supported
- Unlimited Edition
- Enterprise Edition
- Developer Edition
- Professional Edition when purchased with the API add-on (additional installation steps required ONLY if custom profile support has not been purchased from salesforce.com)
More information on installing DupeBlocker in Professional Edition can be found HERE . DupeBlocker cannot be used with Group Edition.
Note: DupeBlocker is a Salesforce Aloha Application therefore the tabs, objects, apps, etc. will NOT count against limits within Salesforce.
Lightning Requirements
Note: Starting in version 3.10, DupeBlocker is Lightning Ready. Users currently running version 3.9 or lower will need to upgrade to 3.10 for full Lightning compatibility.
- To work properly, DupeBlocker uses various custom Lightning Components. Salesforce requires my domain to be enabled in an org in order to use Lightning Components. If My Domain is not currently enabled please follow the instructions in the Salesforce help article Set Up My Domain
- Recommended Browsers: DupeBlocker Lightning works best in Chrome, Safari, and Firefox. Microsoft Edge occasionally results in unexpected errors (not just with DupeBlocker components, but Lightning in general) and therefore we do not recommend DupeBlocker's use in Edge.
- Lightning is supported in DupeBlocker 3.10 and above. Users will need to install/upgrade to the latest release to get started.
Additional configuration steps when using DupeBlocker in Lightning Experience can be found HERE .
Salesforce Storage Requirements
DupeBlocker does require Salesforce storage to maintain a list of "duplicate keys" for each DupeBlocker scenario that is created. The amount of storage needed will depend on the size of the source data and the number of scenarios created. DupeBlocker will take approximately 10% of current storage per object type per scenario. For example, if there are 100MB of Accounts, 100MB of Leads, keys for one Account scenario and one Lead to Account scenario will require 30MB of available storage (~10MB for the Account scenario keys and ~20MB for the Lead to Account scenario keys).
To check existing Salesforce storage by object as well as available free storage go to Setup->Data Management->Storage Usage
The only other storage requirements are for the various DupeBlocker Settings/Mappings (approximately 4.5MB), Scenarios (2KB per scenario), and the DupeBlocker Potential Duplicates, Warning, Task and DupeBlocker Logs (new in version 3.10) objects. The first 3 objects are automatically deleted when duplicates are merged/converted, therefore as long as Warnings are monitored and acted upon in a timely fashion these objects should require very little storage.
DupeBlocker Log records are created automatically whenever a record is merged or converted (either auto or manual) and also whenever an exception error is encountered. These are displayed in the DupeBlocker Logs tab, and can be manually deleted if storage becomes an issue over time (i.e. mass deleted using DemandTools MassEffect, Salesforce Data Loader, or similar mass delete tool).
Starting in Version 3.10, in Lightning Experience, duplicates can be detected when VIEWING a record. Duplicate Warnings will be created to log the duplicates. If users are not managing Warnings, the storage needs for these Warnings and their Potential Duplicate records can accumulate over time. If storage becomes an issue, users have the option to TURN OFF duplicate detection when viewing a record in the DupeBlocker Potential Duplicate Lightning component.
More information on managing warnings can be found HERE .
API Call Requirements
DupeBlocker will require enough API calls to build duplicate keys for matching scenarios. Since Salesforce limits the number of API calls that can be made in a 24 hour period, check this setting in Salesforce to make sure enough calls are available to build the duplicate keys. The number of API calls allowed is based on the Salesforce edition and number of users. The amount of API calls needed to build keys depends on the key building option selected in DupeBlocker Settings -> General Settings.
Note: The duplicate key builder was completely redesigned in DupeBlocker 3. One of the advantages of the new builder is the "Original" key builder uses less API calls than DupeBlocker 2. The "Batch Apex" builder DOES NOT USE ANY API CALLS, but runs about 50% slower than "Original".
Original Key Builder:
The number of calls needed is based on the number of objects in the object(s) keys are being built for. One API call is needed for approximately every 1800 records in the object. The number of deployed scenarios keys are being built for does not increase the number of API calls. Building keys for a single scenario vs. multiple scenarios for the same object type at the same time will use the same number or API calls.
Example 1:
350,000 Accounts
1 or more deployed Account scenarios
Approx 194 API calls (350,000 Account records/1800)
Example 2:
500,000 Accounts
1 million Contacts
3 million Leads
1 or more deployed Account Scenarios
1 or more deployed Lead to Account Scenarios
1 or more deployed Lead to Contact Scenarios
Approx 2500 API calls (4.5 million total records/1800)
Batch Apex: 0 API calls
