I currently have trigger that executes on before insert. I was able to add an error message through the method addError() and was able to display it properly in my visualforce page. As I have read, this should have prevented the insertion of the objects in Trigger.new. But still, the objects are being inserted. How do i prevent the objects from being inserted when an error is added in sObjects?

The purpose of my trigger is to check whether there were records with duplicate name and number. When a user tries to insert new record with the same name and number with an existing record, the page would properly display the error message and would not insert the new record. But when multiple users try to add new records at the same time, this problem occurs. At first it would display that salesforce is not able to get an exclusive access(because another user is trying to access it) but when the user retries to insert new record, new records will be inserted even though there was an error message displayed(the one I have added through addError method).

As an additional information, the trigger.new contains a list of sObjects.

Here is my code for the Trigger:

trigger Testing_Trigger on Sample__c (before insert) {
List<Sample__c> newRecList = Trigger.new;
List<Sample__c> recList;
Set<String> recListNames = new Set<String>();
Map<String, sampleObj> recMap = new Map<String, sampleObj>();

For(Sample__c rec : newRecList){

recList = [Select Name, Rec_No__c from Sample__c where Name IN: recListNames];

For(Sample__c rec : recList){
    sampleObj sObj = recMap.get(rec.Name);
    if(sObj != null){
        sObj = new sampleObj();
        sObj.sRecList = new List<Sample__c>{rec};
    recMap.put(rec.Name, sObj);

For(Sample__c rec : newRecList){
    sampleObj sObj = recMap.get(rec.Name);
    if(sObj == null){
    For(Sample__c sRec : sObj.sRecList){
        If(sRec.Rec_No__c == rec.Rec_No__c){
            rec.addError('Record with the same Name and record number already exists.');

public class sampleObj{
    public List<Sample__c> sRecList{get;set;}
  • 1
    if you can post your code, it would be easy to know what you are doing wrong – Ajay Dubedi Jul 6 '15 at 5:29
  • If the addError executed as you say, there is no way the record should have been created. Can you post your code to examine it further? – RajeshShah Jul 6 '15 at 6:38

First of all, the duplicate checking can be done in a couple of ways:

  1. Use the trigger recipe like this one
  2. Use SFDC OOB Duplicate Management - introduced in Spring(?) 15

As @ajay noted, addError() needs to be used against Trigger.new (or any variable that is a reference to Trigger.new)

Duplicate checking involves checking intrabatch (are there any duplicates within Trigger.new) as well as extraBatch (are there any duplicates when considering records already saved by previous transactions)

You also need to check for duplicates on before insert and before update unless the key fields become read-only after insertion

| improve this answer | |
  • Thank you for your response. As you have suggested, I already have checking functionality for the update of records, posting my whole code here would make the post too long. The 1st option you have suggested would have been useful but my function would have to check for duplicate name AND duplicate record no. AND one more field I have not mentioned before, which means that the function would allow duplicate name as long as it has a different record number and different x field. As for the 2nd option, can you provide a reference link on how i can implement this? – sfDev123 Jul 7 '15 at 1:52
  • see help.salesforce.com/apex/… ; as for option 1, you could adapt the code to handle a composite key but option 2 might be best – cropredy Jul 7 '15 at 17:36

You can use a database savepoint to do this. Sample code:

Savepoint sp = Database.setSavepoint();
try {
    //Do your operations
} catch(Exception e) {
    Trigger.New[0].addError('Your error message');
| improve this answer | |

You are using the line inside a for loop which is iterating on a list.

rec.addError('Record with the same Name and record number already exists.');

To resolve your error, you must use the line in a loop iterating over trigger.new.

| improve this answer | |
  • I am iterating over trigger.new. I have just nested it inside another for loop. Or are you saying that i should put it inside a direct for loop iterating over trigger.new? If I did, can you elaborate what difference that would make? – sfDev123 Jul 7 '15 at 2:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.