 |
 |
 |
 |
| Home > FAQ > General FAQ
General FAQ Index of Questions
Questions and Answers  Can I match on Custom Fields in my DupeBlocker Scenarios? Yes. DupeBlocker 2 now allows matching on any field in Salesforce, both standard and custom. Will DupeBlocker work with Person Accounts? Yes. DupeBlocker 2 has been designed to work with Person Accounts. There are some special customizations required to work properly though. More information on customizing DupeBlocker to work with Person Accounts can be found in DupeBlocker Advanced Functions -> Person Accounts. We have a private sharing model, will DupeBlocker still identify duplicates if the user does not have access to the matching record? Yes, assuming the "Bypass Security" flag is checked in the Scenario Details. Although duplicates will be detected with "Bypass Security" checked, if the user does not have access to a duplicate record, they will receive an insufficient access rights error when they try and view the records. They will also not be able to merge the duplicates from a Warning.More information on Bypass Security can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios -> Scenario Details. If the scenario is set to Auto-Merge or Auto-Convert the records they will be merged or converted. If an Opportunity is created as part of the conversion and the Opportunity Owner is set to either Lead Owner or current user, they will have read only access to the both the Contact and Account, due to the Opportunity being owned by them. I saw in the documentation that DupeBlocker ships with some default scenarios, but I don't see them. How come they are are not showing up? In order to load the default scenarios you need to click on the DupeBlocker Settings tab. This not only loads the defaults scenarios but also all the default settings for the Account Name Filtering List, Nickname Filteing List, Web to Lead Sources and Country Filterering List. After clicking on the DupeBlocker Settings Tab and loaded the defaults, access the DupeBlocker Scenarios tab and select *All" in the View Screen, click "Go" and all the prebuilt scenarios should be displayed.More information on the DupeBlocker Settings Tab can be found in DupeBlocker Installation -> Initial Configuration of DupeBlocker -> DupeBlocker Settings. I just did a bulk insert of records, and I know some probably exist already in Salesforce, how come I did not get any Warnings? DupeBlocker is designed to work for any single insert/update to Salesforce, including records inserted/updated directly through the Salesforce user interface and Web to Lead inserts. It will not trigger blocks or warnings for batch inserts/updates (i.e. third party API applications that process inserts/updates in batch mode, Salesforce Data Loader or Import Wizard), but the duplicate keys created to detect duplicates will be kept up to date. Now that I have setup all my scenarios, is there a way for DupeBlocker to scan all my existing records and identify the existing duplicates? No. DupeBlocker will not detect duplicates that are already in the system, i.e scan the entire database and let you know what duplicates already exist. You need one of CRMfusion's other products, DemandTools, for that. However, if you add a new record that matches to multiple records already in the system, all the records will be included in the Warning message.For more information about DemandTools or other CRMfusion products please visit our website: www.crmfusion.com. We have a significant number of Leads that are a generated via Salesforce Web to Lead, and many are duplicates. Can DupeBlocker be used to detect these duplicates as they are being added to Salesforce? Yes. In fact with DupeBlocker 2 you can also set up scenarios to auto-merge duplicate Leads or auto-convert Leads to matching Contacts or Accounts, if desired. If Scenarios are configured to typically block the insert of a duplicate Lead (i.e. entered by a user directly via the Salesforce User Interface), special handling of Web to Lead inserts has been built in to DupeBlocker to override the block and always create a Warning instead.More information on DupeBlocker's handling of Web to Lead inserts can be found in DupeBlocker Advanced Functions -> Web to Lead. I've setup my scenarios, but for some reason duplicates are not being detected, what am I missing? There are a number of reasons that could be causing duplicates to not be detected, ranging from incomplete initial setup of DupeBlocker, to a misunderstanding of how matching rules are evaluated when looking for duplicates.Setup issues that could be causing the problem:
More information on Mapping Types and Options can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios -> Mapping Types Described in Detail. Can DupeBlocker be configured to only trigger for specific users? Yes. DupeBlocker 2 includes the ability to create Filters to limit when a DupeBlocker Scenario will be triggered. Filters can be based on attributes of the object itself (i.e. based on Country or Lead Source) or attributes of the user entering the new record (i.e. based on user id, name, role or profile).More information on creating Filters can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios -> Scenario Filters. Is there a way to configure DupeBlocker to "run in the background" without my users being aware of duplicates being detected? Yes. DupeBlocker can be customized such that only System Administrators or DupeBlocker Administrators manage the detected duplicates.Here are customizations that would accomplish this. Some or all of the steps can be followed depending on exactly how user access should be limited.
More information on these customizations can be found in DupeBlocker for the End User. I want my users to be aware that duplicates are being detected, but I DO NOT want them to be able to merge or convert any records. How can this be accomplished? There are a couple of different options to accomplish this:
Can I make someone that is not a System Administrator a DupeBlocker Administrator with access to the DupeBlocker Tab? Yes. Any non-admin profile(s) can be set-up as a DupeBlocker Administrator, by selecting "DupeBlocker Administrator" under "Access Level" for a specific profile per "Step 3(Salesforce Step 2): Choose Security Level" when installing or upgrading DupeBlocker. DupeBlocker Administrators will have full access to the DupeBlocker application including the ability to create/modify scenarios, monitor all warnings, merge/convert duplicates etc.More information on choosing the security level during installation can be found in DupeBlocker Installation -> Installing DupeBlocker. If this was not done during installation, the Salesforce profile permissions can be updated as follows to make a profile a "DupeBlocker Administrator":
How come I see multiple Warnings after inserting/updating just one record? Warnings will be created for each scenario that triggers a potential duplicate. Therefore, it is possible to have multiple warnings generated for one insert/update. For example:
If a new Lead is inserted that matches another Lead AND ALSO matches an existing Contact and I have Lead "auto-merge" and Lead to Contact and Lead to Account "auto-convert" scenarios, what will happen to the Lead? The new Lead will be auto-converted into the existing Contact. The order of operations for "Match on Insert Action" is as follows:Auto-Convert (Lead to Contact over Lead to Account) Auto-Merge Blocks ("Do Not Insert", "Redirect to Existing") Warnings ("Report Duplicate") Note: If the "Match on Update Action" is set to "Report Duplicate" on the Lead to Contact scenario, then after the auto-conversion is complete a Warning WILL BE CREATED alerting the user that there is still a Lead (the existing one) that matches the existing Contact. |
 |
 |
 |
Print