Important DupeBlocker Notification regarding upcoming Summer '13 Release
Monday, May 13, 2013
Please note an upcoming change in the Salesforce Summer '13 release could affect the current version of DupeBlocker. This change will effect most DupeBlocker customers as it effects anyone using DupeBlocker's “Do Not Insert”, “Do Not Update”, or “Redirect to Existing” action calls after duplicate detection.
The background of the issue is that prior to Summer ’13, Salesforce allowed the ability to escape HTML code in error messages. In Summer ’13 there is a critical update that the administrator has the option to activate which will disable this capability. As a result the Redirect to Existing functionality will no longer work at all, and the error message displayed by DupeBlocker when a duplicate is blocked via “Do Not Insert/Update” will render the full HTML code as text in the user interface.
Duplicates will still be blocked, but the error message defined in the scenario will not be displayed properly.
Example current message:
Error: Invalid Data.
Review all error messages below to correct your data.
Potential duplicate Lead found with a similar name and the same e-mail address. Duplicate: John Smith
Review all error messages below to correct your data.
Potential duplicate Lead found with a similar name and the same e-mail address. Duplicate: John Smith
Summer ’13 message (note: only the first few lines are displayed):
Error: Invalid Data.
Review all error messages below to correct your data.
<script type="text/javascript"> <!-- var appendParam = ""; if ( document.location.href.toLowerCase().indexOf( "?isdtp=" ) >= 0 ||
Review all error messages below to correct your data.
<script type="text/javascript"> <!-- var appendParam = ""; if ( document.location.href.toLowerCase().indexOf( "?isdtp=" ) >= 0 ||
We will be updating DupeBlocker to accommodate this change, but unfortunately will not be able to begin work on the upgrade until our own Developer Edition instance is upgraded to Summer ‘13 - which could be the same day or after certain customer environments could have possibly already applied the critical update. We anticipate having a DupeBlocker upgrade available approximately one week after our development instances are upgraded and we will notify all customers at that time suggesting that they install the upgrade.
To avoid any changes in DupeBlocker behavior after your Salesforce instance has been upgraded to Summer ‘13, we highly recommend that admins DO NOT apply the critical update until our DupeBlocker upgrade is available. Please keep in mind that critical updates can also be disabled, therefore, if it is applied by an administrator that is unaware of the implications to DupeBlocker it can subsequently be disabled.
All customers WILL eventually need to upgrade their DupeBlocker application though, as at some point Salesforce will apply the critical update to all instances by default.
Please contact our support department via support@crmfusion.com , if you have any questions.
posted by A Miller @ 4:12 PM,
