QUESTION:
We are an NFP and are using the HEDA model (Higher Education Data Architecture) from Salesforce.org. I have set-up a Contact scenario to catch new contacts being inserted, but it does not seem to be working. How can I resolve?
ANSWER:
In HEDA when a Contact is created with no Account specified an "Administrative" Account automatically gets created FIRST then the Contact is created and linked to the Account.
DupeBlocker will ONLY trigger for the first object being affected in the same Apex batch so as to avoid exceeding governor limits. In the case of HEDA the first object inserted is the Account and not the Contact. As a result DupeBlocker DOES NOT trigger the “Match on Insert Action” for a Contact scenario. However, doing an update on the same record DOES trigger the “Match on Update Action".
Even if the Account was manually entered first, then the Contact as added to that Account, the "Match on Insert Action" still does not fire as it seems HEDA does and update of some kind to the existing Administrative account BEFORE inserting to Contact. So the Account object is still affected prior to the Contact being inserted.
There is no workaround for this issue so unfortunately it will not function correctly with this template.