QUESTION:
I am getting the following error when testing my DupeBlocker scenarios and the duplicates are not being caught, how can I resolve?
DupeBlocker has encountered an error. Please contact your Salesforce administrator with the following information:
*** Trigger: Account after update
*** isMerge value: false
*** Trigger.new size: 2
*** Trigger.old size: 2
*** Exception Type: System.SObjectException
*** Exception Cause: null
*** Exception Message: Invalid field name for Account
ANSWER:
This error is due to not configuring DupeBlocker to work correctly with Person Accounts.
Since the "Account Name" field in Person Accounts is actually a formula field, when creating Scenario Rules for matching on name, the "First Name" and/or "Last Name" fields should be used instead of the "Account Name" field. Using the "Account Name" field will result in the "Invalid field name for Account " error.
When Person Accounts are enabled in an organization, Account and Lead to Account scenarios should be created separately for Business Accounts vs. Person Accounts.
***If using version 2.19 or lower, this can be done with the use of DupeBlocker Filters filtering on the "Is Person Account" field in Salesforce being either True or False.
True: Person to Person Account
False: Business to Business Account
***If using version 2.20 or higher, this can be done with the NEW "Person Account Scenario" checkbox field on the Scenario Detail Section
Checked: Person to Person Account
Unchecked: Business to Business Account
Both Account AND any Lead to Account Scenarios need to be customized.
More details on how to configure DupeBlocker to function correctly with Person Accounts can be found here.