Home/ Questions/Q 720201
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:43:53+00:00

I’m trying to write an after update trigger that does a batch update on

  • 0

I’m trying to write an “after update” trigger that does a batch update on all child records of the record that has just been updated. This needs to be able to handle 15k+ child records at a time. Unfortunately, the limit appears to be 100, which is so far below my needs it’s not even close to acceptable. I haven’t tried splitting the records into batches of 100 each, since this will still put me at a cap of 10k updates per trigger execution. (Maybe I could just daisy-chain triggers together? ugh.)

Does anyone know what series of hoops I can jump through to overcome this limitation?

Edit: I tried calling following @future function in my trigger, but it never updates the child records:

global class ParentChildBulkUpdater
{
    @future 
    public static void UpdateChildDistributors(String parentId) {
        Account[] children = [SELECT Id FROM Account WHERE ParentId = :parentId];

        for(Account child : children)
            child.Site = 'Bulk Updater Fired';
        update children;

    }
}
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s worst than that, you’re not even going to be able to get those 15k records in the first place, because there is a 1,000 row query limit within a trigger (This scales to the number of rows the trigger is being called for, but that probably doesnt help)

    I guess your only way to do it is with the @future tag – read up on that in the docs. It gives you much higher limits. Although, you can only call so many of those in a day – so you may need to somehow keep track of which parent objects have their children updating, and then process that offline.

    A final option may be to use the API via some external tool. But you’ll still have to make sure everything in your code is batched up.

    I thought these limits were draconian at first, but actually you can do a hell of a lot within them if you batch things correctly, we regularly update 1,000’s of rows from triggers. And from an architectural point of view, much more than that and you’re really talking batch processing anyway which isnt normally activated by a trigger. One things for sure – they make you jump through hoops to do it.

    • 0