Home > DupeBlocker Installation > Upgrading to DupeBlocker 2 (1.X to 2.X)

Upgrading to DupeBlocker 2 (1.X to 2.X)

Only Record Type versions of DupeBlocker 1.X can be upgraded to DupeBlocker 2.  If an earlier 0.9.X version of DupeBlocker or any non Record Type version is installed, an uninstall of the previous version and re-install of the DupeBlocker 2 version will be required.  Upgrading vs. uninstall/reinstall will keep most customizations intact including updates to Lead, Contact and Account page layouts, DupeBlocker Settings, Scenario updates etc. Additionally, outstanding Warnings will not be deleted, and DupeBlocker keys will not need to be rebuilt.

Please note additional configuration Step 6 which applies to upgrades only.  Review of Step 6 is recommended PRIOR to choosing an upgrade vs. a reinstall.

Step 2 (Salesforce Step 1):  Approve Package API Access



Click "Next".

Step 3 (Salesforce Step 2):  Choose Security Level 



Step 1:  Choose security level

Select the "Select Security Settings" radio button.

Step 2:  Customize security 

Select "Set All" for Non-admin users.

Starting with Salesforce Spring '10, all standard Salesforce profiles will not have access to the DupeBlocker custom objects and CANNOT be updated to gain access.  In order for users to have access to the DupeBlocker objects they will need to be assigned a custom profile.  Existing custom profiles will be assigned "Read" only access to the following DupeBlocker Objects:

Warnings
Potential Duplicates
Scenarios
Filters
Rules

Step 3:  Access Level

Optionally, update the access level for specific non administrator profiles to "DupeBlocker Administrator" for profiles that should have full access to the DupeBlocker application including the ability to create/modify scenarios, monitor all warnings etc.

Click "Next".

More information on customizing profiles to support DupeBlocker can be found in DupeBlocker Installation -> Initial Configuration of DupeBlocker -> Customizing Profiles.

Step 4 (Salesforce Step 3):  Install Package

Check the box for "Ignore Apex test....." to avoid potential install problems due to required field settings in Salesforce that will not be detected during the installation tests (i.e. if the default setup for required fields in Salesforce have been altered).



Click "Install".

The upgrade is now installed, follow the instructions to redeploy the upgraded version.

Note:  Typically a message is generated from Salesforce that the package is being installed, and that an email will be sent when complete.  In this case once the message is received, go to Setup->Develop->View Installed Packages and then follow the steps to deploy.

Undeployed packages WILL work correctly for System Administrators, but WILL NOT function for users with non-administrator profiles.

Step 5:  Deploying DupeBlocker



Click "Deploy" to deploy the application.



Click "Deploy".

1. Go to Setup->Create->Objects and click on DupeBlocker Scenario.  Scroll down to Page Layouts and edit the "DupeBlocker Scenario Admin Layout".
2. In the "Fields" section: Remove the "Match on Insert Result" and "Match on Update Result" fields and replace them with the "Match on Insert Action" and "Match on Update Action" fields below "Deployed".  Click the tool icon  on each field to make them required.
3. In the "Buttons" section: Add the "Auto-Merge/Convert Settings" button to the Custom Buttons area of the detail section.  Put the new button to the left of "Rebuild Keys" buttons.
4. In the "Related Lists" section:  Add the "DupeBlocker Scenario Filters" related list after the "DupeBlocker Scenario Rules" list.
5. Edit the "DupeBlocker Scenario Rules" related list properties replacing "Match Field" with "Field" and add "Related Field" after "Mapping Type".  “Field” goes between "Rule Number" and  "Mapping Type".   Make sure you have "DupeBlocker Scenario End User Layout" checked under "Apply column information to other page layouts:" and click OK.
6. Edit the "DupeBlocker Scenario Filters" related list properties.  Add the "Filtered Object", "Filtered Field", "Operator" and "Criteria" fields in that order.
7. Change "Sorty By:" to "Filter Number" and click OK.  Leave as ascending.
8. Click "Quick Save" at the top of the page to save the current profile and override end user customizations if prompted.
9. Scroll up to the top of the page and click on "DupeBlocker Scenario Admin Layout" then select "DupeBlocker Scenario End User Layout".
10. In the "Fields" section: Remove the "Match on Insert Result" and "Match on Update Result" fields and replace them with the "Match on Insert Action" and "Match on Update Action" fields below "Deployed".  Click the tool icon  on each field to make them required.
11. In the "Related Lists" section:  Add the "DupeBlocker Scenario Filters" related list after the "DupeBlocker Scenario Rules" list.
12. Edit the "DupeBlocker Scenario Filters" related list properties. Add the "Filtered Object", "Filtered Field", "Operator" and "Criteria" fields in that order.
13. Change "Sorty By:" to "Filter Number".  Leave as ascending.
14. Click on the "Buttons" section and unselect the "New" button, then click OK.
15. Save the current page layout and override end user customizations if prompted.
16. Rebuild keys for a scenario or edit a record that would trigger DupeBlocker to check for duplicates.  This will cause DupeBlocker to upgrade your existing scenarios and rules.

The resulting DupeBlocker Admin Scenario Page Layout should look like this (the End User layout will look the same EXCEPT for NO buttons).  The arrows indicate what was added or changed:

Note:  If upgrading from 1.0.2 to a later version, click on the DupeBlocker Settings tab and enter an email address in the NEW "General Settings" tab to receive DupeBlocker exception emails.    If left blank, the current user will be notified. More information on customizing DupeBlocker Settings can be found in DupeBlocker Installation -> Initial Configuration of DupeBlocker -> DupeBlocker Settings.

See also