[SalesForce] How to make the trigger only fire after all (of several thousand) records are finished being inserted

I have a batch apex class that I need to fire only after all of the thousands of records from a record import have been inserted into a custom object. I thought I should use a trigger to fire my batch apex job.

I read somewhere though that the trigger would execute once for every 200 records that were inserted which I think would fire my batch apex multiple times. This is a problem because in the finish method of my batch apex, I need to execute a different batch apex job which will operate on the results of a grouping query of the same custom object's records and must take into account all of the newly inserted records at once.

Best Answer

You can put the call to the trigger code in an IF statement so that by changing one value (in this case "AppFn.s_bIsTriggerActive"), you can turn off trigger processing to allow for things like the bulk uploading of records.

If you use this technique, be certain to do it outside of normal business hours. You don't want data entered by regular users to escape the trigger processing too.

Trigger OnCustomObjectChangeTrigger on CustomObject__c(after insert, after update, after delete, after undelete)
{
   if(AppFn.s_bIsTriggerActive)
       OnCustomObjectChange.OnCustomObjectChanged();
}

Related Solutions

[SalesForce] Delaying Trigger until all related records are inserted

Create a web service method, and have your client code call that method. Use a static variable to keep your trigger from firing when using this web service.

global class WebServices {
    static webservice String createInvoice(InvoiceData data) {
        String result;
        try {
            executeTrigger = false;
            // Insert Invoice
            // Insert Line Item
            // Insert Revenue
        } catch(exception e) {
            result = 'failed: '+e.getMessage();
        }
        return result; // 
    }

    global class InvoiceData {
        // describe invoice data
    }

    global static boolean executeTrigger = true; // for non-ws updates
}

Edit: You could also use REST instead of SOAP; the end result is the same.

[SalesForce] Loading 1 million records using bulk API: Exceeding batch Limit

So I think the problem is that the bulk data API is running multiple asynchronous batches and thus kicking off too many Batchable Contexts.

It looks like your batch process doesn't actually care what Id's you pass in and instead just processes everything?

If this is the case and you don't need real time (or close to realtime) updates, it might be a better idea to just schedule this to run.

Otherwise, if you need it to happen in near real time, you could use batch "chaining" in order the have the batch keep running as long as there are records to process.

The basic steps would look something like this:

In the finish method, add a check to see if there are more records to process. If so kick off another batch.
In your trigger, have it first check if the batch is already running. If so, you don't need to do anything. Otherwise, have it kick off the batch.

Update

If you have access to the JobInfo concurrencyMode param, you can set this to "Serial" and it will prevent multiple batches from running in parallel. I think this might solve you problem. If that alone doesn't work, try also reducing the batch size. Obviously, this will cause the import to take much (much) longer.

On the dataloader this Serial can be turned on by checking "Enable Serial Mode for Bulk Api".

Best Answer

Related Solutions

[SalesForce] Delaying Trigger until all related records are inserted

[SalesForce] Loading 1 million records using bulk API: Exceeding batch Limit

Update

Related Topic