New answers tagged

0

You need to bulkify your code, try not to put logic in the trigger, move the logic to a handler/helper. Also avoid doing DML operations inside a loop, you're going to hit another limit soon. // ProgTrigger ProgTriggerHandler.handleEnrollmentDeletion(Trigger.NEW); // ProgTriggerHandler#handleEnrollmentDeletion Map<Id, hed__Program_Enrollment__c > ...


4

I assume, delete dml invokes some trigger in managed package, which throws an SOQL limit exception. Overall, it is possible to use dml not for the single record, but for the collections of the records. Move delete prog; outside of the loop trigger ProgTrigger on hed__Program_Enrollment__c (before insert) { list<hed__Program_Enrollment__c> ...


1

The default behavior would be the child gets a Before Update trigger, then a After Update trigger. The parent record would not ordinarily fire. This is the vanilla behavior. I'm presuming you've read the logs wrong, because the absolute first trigger to fire would need to be the child's Before Update trigger. From there, all bets are off. A before update ...


Top 50 recent answers are included