#TDTM0 人がディスカッション中

***reposting from another TB group to see if it gets better answers here**

Summary of Issue

• I received an Apex trigger error email when trying to create a lead as a Guest User from my Experience Cloud Site using the OOTB 'Lead Form' component in the Experience Builder.

EMAIL ERROR MESSAGE

npsp.TDTM_Lead : npsp.TDTM_Lead: execution of BeforeInsert caused by: line 33, column 5: Variable does not exist: TDTM_Config_API

Troubleshooting steps already taken

• I checked the list of all Table-Driven Trigger Management (TDTM)" Apex class handlers in the NPSP Settings > System Tools > Trigger Configuration
  • NO class 'npsp.TDTM_Lead' exists.
  • Class 'TDTM_Config_API' does exist, but it is not available as a Trigger Handler setting to disable.

Additional context/details

• I have implemented a 'Create a Lead' Form component in my Experience Cloud Site for Unauthenticated Guest Users. I mapped the required field and some other fields within the component from the Experience Builder.
• I configured all the necessary S&S / permissions and other setup steps needed, then published the site.
• We have NPSP installed.
• The Experience Cloud Site with the Lead From is for Guest Users to create Leads.

#Experience Cloud #Forms #Leads #NPSP #Triggers #NPSP TDTM #TDTM

We are using EDA and want to extend the TDTM functionality with an additional class on the Affiliation object. This class should evaluate if an Affiliation's primary checkbox field was previously TRUE and was changed to FALSE. If so, it should change the values of status and end date on the Affiliation. Our goal is that when the aligned Primary Affiliation field on the Contact is changed, the Affiliation record that is "unchecked" (formally the primary record but no longer) has an end date added and the status gets changed.

I created my class, added an entry to the Trigger Handler object, and have activated the class. However whenever I try to change the Primary Affiliation field on the Contact, I get the following error:: "System.SObjectException: DML statement cannot operate on trigger.new or trigger.old"

I have also pasted my code below, any help is appreciated. I'd like assurance that I have extended the TDTM functionality correctly, as the documentation is sparse and the error appears to be with how the class is trying to DML the record.

//

global class Aff_Extend_TDTM extends hed.TDTM_Runnable {

global override hed.TDTM_Runnable.DmlWrapper run(

List<Sobject> newlist,

List<SObject> oldlist,

hed.TDTM_Runnable.Action triggerAction,

Schema.DescribeSObjectResult objResult) {

hed.TDTM_Runnable.DmlWrapper dmlWrapper = new hed.TDTM_Runnable.DmlWrapper();

list<hed__Affiliation__c> loadAff = new list<hed__Affiliation__c>();

// Cast the trigger.new and trigger.old list into an Affiliation__c list

List<hed__Affiliation__c> triggernew = (list<hed__affiliation__c>)newlist;

List<hed__Affiliation__c> triggerold = (list<hed__affiliation__c>)oldlist;

// Make trigger.oldmap from triggr.old list

Map<Id, hed__Affiliation__c> triggeroldmap = new Map<Id, hed__Affiliation__c>();

for ( hed__Affiliation__c aff1 : triggerold )

triggeroldmap.put(

, aff1);

if (triggerAction == hed.TDTM_Runnable.Action.BeforeUpdate) {

// Compare values and determine if box was unchcked in this run

for (hed__Affiliation__c aff2 : triggernew ) {

hed__Affiliation__c oldAff = triggeroldmap.get(

);

if(aff2.hed__Primary__c != oldAff.hed__Primary__c) {

System.debug('--* Aff Primary is changed*--');

aff2.hed__status__c = 'former';

aff2.hed__enddate__c = date.today();

loadAff.add(aff2);

}

}

dmlWrapper.objectsToUpdate.addAll((list<SObject>)loadAff);

}

return dmlWrapper;

}

}

I've read the TDTM documentation, done some web searching, and perused a bit of the code. I still have some technical questions. (I see that there are questions here with a TDTM topic, but it wasn't one of the choices in the "Add topics" section when I created this question.)

1. I've seen other questions raised here about whether the trigger handlers are processed in the same order in a test as they are normally. This appears to have something to do with how the data is loaded into the triggerHandlers variable in the test class, i.e. the fact that the handler being tested is loaded last, and therefore isn't necessarily in the Load Order. Is this the case, i.e. are there differences, and if so, why? How do we ensure we're testing the same order as will be live?

2. On a related note, the sample test code shows making a call to get the "default" records, then adding the class being tested to the local triggerHandlers variable. But, related to #1, if we have more than one additional handler in production, and they're not loaded in the test class for handler X, then we're again not testing what's actually going to run in a live environment. Shouldn't we load *all* of our handlers into the variable in a test class? (This is more theoretical for us at the moment, but I want to know how to deal with it going forward.)

3. The call to get the cached records in fact inserts the "default" TDTM records into the trigger handler table. So after the call, they're loaded in the table, and we have them in the triggerHandlers local list variable. We then load our handler being tested into that variable. But it's not in the table. I'm missing how just having it in a local variable is causing it to be called during testing.

4. The sample test class is obviously a simple one, and shows everything happening in a single method. But because I'm not clear on #3 above, I'm not clear what we can do. Is it OK to still use a testSetup method to load the test data needed by the other test methods? Does any test method that needs to do DML need to load the triggerHandlers variable?

Thanks for any help and/or pointers!