5
As at the time of writing there is a bug with how triggers on BatchApexErrorEvent can be packaged. Or more specifically, that they can't be packaged.
There is a thread about it in the Partners managed packages success group.
...there is now a feature request opened with the Platform Events team [...] to add package support for triggers on standard ...
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> ...
3
Unfortunately as it stands right now there is no way to do this utilizing the public SFMC API (neither SOAP nor REST). You, as an end user will need to utilize the UI to activate/deactivate a file drop Automation.
There is an internal rest endpoint (use developer tools on your browser, click on network tab in dev tools and then toggle your automation off/on)...
3
There are several different approaches you can use to test your trigger and attempt to isolate the bugs.
Manual Testing
Manual testing boils down to performing record creation or update steps within the user interface (or via Anonymous Apex) that cause your trigger to run and yield you some information, whether that information comes via an exception ...
1
You should use Workflow Rule here, not Apex. Specifically, Add a Time-Dependent Action to Your Workflow Rule:
Time-dependent actions are executed at a specific time, such as 10 days before a record’s close date. When that specific time passes, the workflow rule re-evaluates the record to make sure that it still meets the rule criteria. If the record does, ...
1
Although this can be achieved using Apex Triggers, this functionality can be accomplished via a declarative tool such as a Process Builder or a Workflow Rule.
In order to do so, write a Process Builder or Workflow Rule that executes when a new Salesforce_Ticket__c record is created or updated. The criteria for execution would be as follows
AND(
...
1
Off the bat you want to avoid using a DML statement (the update) in a for loop; keeping it in the loop will cause you to run into governor limits. To avoid this, before you iterate the 'spList' you should initialize an empty list of type Salesforce_Project__c, this list will be all the Salesforce Projects you are updating. Add the new SPs to this list while ...
Only top voted, non community-wiki answers of a minimum length are eligible
