Hi everyone - I have a client using both the NPSP version 3 and CQ RollCall's Engage integration. Engage is an online advocacy and outreach tool. With the integration, all actions and people entered into Engage are supposed to sync with Salesforce through an automated import. However, the sync fails because of a "too many DML statements" error on the Contact object. Apparently there's too much code running at once, batch size is too big, or both.
My question is, can I used TDTM to help resolve the issue? Is it just a matter of reordering triggers, having them run asynchronously, or maybe even disabling triggers? Does the Engage package just need its own Trigger Handler? I'm not too familiar with how to troubleshoot this specific issue. If it helps, here's the message I got from Engage support:
“We found an error message that reads "First error:npsp:Too many DML statements:151". NPSP is the namespace of Non-Profit Starter Pack. This indicates that the issue is raised from code that belongs to Non Profit Starter Pack (another managed package installed in this client’s Salesforce org). There is a trigger on the Contact object from the NPSP package. When Engage creates Contact records in bulk, this error message is thrown from the NPSP trigger.”
@System Administrators
@Nonprofit Salesforce Developers
@Advocacy (ARCHIVED)
I'd like to move this conversation to "Any update on CQ Roll Call Engage SF sync work?" in the Advocacy public group, but acknowledge that there is a lot of useful background in this one.
