Hi all,

I'm stuck on creating a validation rule for a custom object. Bascially, the object is a form with a bunch of account lookup relationships and I need to make sure that the same account is not selected more than once. To make things a little more complicated, sometimes there will be several records (linked by the same custom parent object) and I also want to prevent duplicate accounts being selected across records of the same parent.

I can isolate all the accounts that I want to make sure aren't duplicated in the object records and send them to a list, but I don't know of an efficient way to actually pick up on a duplicate. Is there a method that already exists that will check for duplicates in a list? I don't need specific code, just the general idea of how I might do this.

Thanks,

Andrew
 

Hello All,
I'm writing test for a trigger, but when I create the test data, I cannot get any id values to pass to the required fields (highlighted) on my custom object. The test class will save, but fails when I run it, saying that the required fields are missing on the insert. Any ideas why it won't update these fields? Here is the Test Class:

Hi everyone,

I have a requirement that needs me to link a user id field on a custom object to another user id field on the opportunity object. When the id field is updated from either object, I want the corresponding field on the other object to update with the same user. The custom and opportunity objects are connected to each other by two lookup relationship fields. (Implementation__c on the Opportunity and Opportunity__c on the custom object)  These are the two triggers I wrote:

1 trigger UpdateESS on Opportunity (after insert, after update) {
2
3      List<ID> ImpIds = New List<ID>();
4
5       for(Opportunity o : Trigger.new){
6       if(o.Assigned_trainer__c != null && o.Implementation__r.Education_Support_Specialist__c  == null){
7           ImpIds.add(o.Implementation__c); 
8       } 
9   }
10     
11   
12  List<Implementation__c> ImpList = [SELECT id, Education_Support_Specialist__c, opportunity__c FROM Implementation__C WHERE id in :ImpIds];
13   
14   Map<id,Opportunity> mImptoOpp = New Map<id,Opportunity>();
15       for(Opportunity k : trigger.new){
16           if(k.Assigned_Trainer__c != null && k.Implementation__r.Education_Support_Specialist__c == null){ 
17               mImptoOpp.put(k.implementation__c, k);              
18           }
19       }    
20  for(integer i = 0 ; i < ImpList.size(); i++){ 
21    ImpList[i].Education_Support_Specialist__c = mImptoOpp.get(ImpList[i].id).Assigned_Trainer__c;
22    }        
23 Update ImpList;
24 }

1 trigger UpdateAssignedTrainer on Implementation__c (after insert, after update) {
2
3   List<ID> OppIds = New List<ID>();
4
5   for(Implementation__c o : Trigger.new){
6       if(o.Education_Support_Specialist__c != null && o.Opportunity__r.Assigned_Trainer__c == null){
7           OppIds.add(o.Opportunity__c);  
8       } 
9   }  
10   
11   List<Opportunity> OppList = [SELECT id, Assigned_Trainer__c, implementation__c FROM Opportunity WHERE id in :OppIds];
12   
13   Map<id,Implementation__c> mImptoOpp = New Map<id,Implementation__c>();
14       for(Implementation__c k : trigger.new){
15           if(k.Education_Support_Specialist__c != null && k.Opportunity__r.Assigned_Trainer__c  == null){ 
16               mImptoOpp.put(k.Opportunity__c, k);
17           }
18       } 
19   
20 for(integer i = 0 ; i < OppList.size(); i++){ 
21    OppList[i].Assigned_Trainer__c = mImptoOpp.get(OppList[i].id).Education_Support_Specialist__c; 
22    } 
23 Update OppList;  
24 }

The two triggers are essentially identical, except they are initiated by and update the opposite object. The issue I'm having (at least I think this is what's happening) is that the DML statement that saves the changes to the database actually causes the other trigger to fire, creating the infinite loop.  I tried adding conditions to the trigger that would prevent the loop, but I think the trigger executes before the new data value can be comitted to the database. Is it possible to stop the DML statement from firing the second trigger? Could combining these triggers resolve the issue? Any advice would be much appreciated.

Here's the actual error in case I am misunderstanding what is happening:

Error:Apex trigger UpdateESS caused an unexpected exception, contact your administrator: UpdateESS: execution of AfterUpdate caused by: System.DmlException: Update failed. First exception on row 0 with id a0BW000000JNK7aMAH; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, UpdateAssignedTrainer: maximum trigger depth exceeded Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a]: []: Trigger.UpdateESS: line 23, column 1

Hi all,

I'm stuck on creating a validation rule for a custom object. Bascially, the object is a form with a bunch of account lookup relationships and I need to make sure that the same account is not selected more than once. To make things a little more complicated, sometimes there will be several records (linked by the same custom parent object) and I also want to prevent duplicate accounts being selected across records of the same parent.

I can isolate all the accounts that I want to make sure aren't duplicated in the object records and send them to a list, but I don't know of an efficient way to actually pick up on a duplicate. Is there a method that already exists that will check for duplicates in a list? I don't need specific code, just the general idea of how I might do this.

Thanks,

Andrew
 

Hello All,
I'm writing test for a trigger, but when I create the test data, I cannot get any id values to pass to the required fields (highlighted) on my custom object. The test class will save, but fails when I run it, saying that the required fields are missing on the insert. Any ideas why it won't update these fields? Here is the Test Class:

Hi everyone,

I have a requirement that needs me to link a user id field on a custom object to another user id field on the opportunity object. When the id field is updated from either object, I want the corresponding field on the other object to update with the same user. The custom and opportunity objects are connected to each other by two lookup relationship fields. (Implementation__c on the Opportunity and Opportunity__c on the custom object)  These are the two triggers I wrote:

1 trigger UpdateESS on Opportunity (after insert, after update) {
2
3      List<ID> ImpIds = New List<ID>();
4
5       for(Opportunity o : Trigger.new){
6       if(o.Assigned_trainer__c != null && o.Implementation__r.Education_Support_Specialist__c  == null){
7           ImpIds.add(o.Implementation__c); 
8       } 
9   }
10     
11   
12  List<Implementation__c> ImpList = [SELECT id, Education_Support_Specialist__c, opportunity__c FROM Implementation__C WHERE id in :ImpIds];
13   
14   Map<id,Opportunity> mImptoOpp = New Map<id,Opportunity>();
15       for(Opportunity k : trigger.new){
16           if(k.Assigned_Trainer__c != null && k.Implementation__r.Education_Support_Specialist__c == null){ 
17               mImptoOpp.put(k.implementation__c, k);              
18           }
19       }    
20  for(integer i = 0 ; i < ImpList.size(); i++){ 
21    ImpList[i].Education_Support_Specialist__c = mImptoOpp.get(ImpList[i].id).Assigned_Trainer__c;
22    }        
23 Update ImpList;
24 }

1 trigger UpdateAssignedTrainer on Implementation__c (after insert, after update) {
2
3   List<ID> OppIds = New List<ID>();
4
5   for(Implementation__c o : Trigger.new){
6       if(o.Education_Support_Specialist__c != null && o.Opportunity__r.Assigned_Trainer__c == null){
7           OppIds.add(o.Opportunity__c);  
8       } 
9   }  
10   
11   List<Opportunity> OppList = [SELECT id, Assigned_Trainer__c, implementation__c FROM Opportunity WHERE id in :OppIds];
12   
13   Map<id,Implementation__c> mImptoOpp = New Map<id,Implementation__c>();
14       for(Implementation__c k : trigger.new){
15           if(k.Education_Support_Specialist__c != null && k.Opportunity__r.Assigned_Trainer__c  == null){ 
16               mImptoOpp.put(k.Opportunity__c, k);
17           }
18       } 
19   
20 for(integer i = 0 ; i < OppList.size(); i++){ 
21    OppList[i].Assigned_Trainer__c = mImptoOpp.get(OppList[i].id).Education_Support_Specialist__c; 
22    } 
23 Update OppList;  
24 }

The two triggers are essentially identical, except they are initiated by and update the opposite object. The issue I'm having (at least I think this is what's happening) is that the DML statement that saves the changes to the database actually causes the other trigger to fire, creating the infinite loop.  I tried adding conditions to the trigger that would prevent the loop, but I think the trigger executes before the new data value can be comitted to the database. Is it possible to stop the DML statement from firing the second trigger? Could combining these triggers resolve the issue? Any advice would be much appreciated.

Here's the actual error in case I am misunderstanding what is happening:

Error:Apex trigger UpdateESS caused an unexpected exception, contact your administrator: UpdateESS: execution of AfterUpdate caused by: System.DmlException: Update failed. First exception on row 0 with id a0BW000000JNK7aMAH; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, UpdateAssignedTrainer: maximum trigger depth exceeded Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a] Opportunity trigger event AfterUpdate for [006W000000605S1] Implementation trigger event AfterUpdate for [a0BW000000JNK7a]: []: Trigger.UpdateESS: line 23, column 1