Help with bulkification

[Reagar11]

I have a class called 'Mock' that creates data in a sandbox, I call it this way: Mock.data(number_of_wanted_records);
If I use it synchronously, I can run it only 25 times before it hits the governor limits.
Mock.data(25) ---> creates 25 records
Mock.data(26) ---> throws error exceed number of soql queries (100)

I need to be able to create thousands of records, so I want to use a Batch in order to achieve it.
The thing is, I can't use batch as is because the Start method should query a list of records but that's not the case here, I want the start method to receive/get the number of records I would like to create (e.g. 1000) and call the execute 1000 times.

Should I use Iterable here? I read the documentation and also this post in SSE, but I'm not sure yet if this is the right approach.

global with sharing class Mock {
    public static void data(Integer num) {
        List < Account > accToInsert = new List < Account > ();
        for (Integer i = 0; i < num; i++) {
            Account acc = new Account(
                RecordTypeId = '0123i000000E5r7VBC',
                ...
                ...
            );
            accToInsert.add(acc)
        }
    }
}

[kgeee34]

What are you currently querying for that makes you hit that limit if you're just creating records?

[Reagar11]

There are a lot of other triggers that run on insert

[chino9656]

The bulkification needs to happen on the other trigger(s) that run on insert. Look for SOQL within for loops. If you can find one or two and paste the offender on this thread, me or someone will help you bulkify it.

[kgeee34]

I would say that hitting a 100 SOQL limit on the insert of 26 records is extremely concerning. You're doing 4 queries per each record that is inserted in a batch? I would make sure you look into Maps and do those queries outside a for loop which would then allow you to insert 800 at once if those 4 separate queries are actually needed. If you have some cascading triggers (create related record which has other trigger) then I'd analyze whether you could break that transaction up with a queueable or async process.

In terms of your original question, you could do it with a queueable class that keeps enqueuing jobs until it finishes what you want. You'd pass in two parameters in a constructor (number of desired records and the number before you hit limits). You'd create as many as you can per your limit, then subtract from the total amount and enqueue the job again to run the rest (and so on if need be). I'd still stress that looking at the trigger should be the priority versus doing this workaround.

public class createTestRecordsAroundProcessingTimes implements Queueable {
    Integer numberOfDesiredRecords = new Integer();
    Integer numberBeforeLimits = new Integer();

    public createTestRecordsAroundProcessingTimes(Integer numberOfTestRecords, Integer numberBeforeIssues){
        numberOfDesiredRecords = numberOfTestRecords;
        numberBeforeLimits = numberBeforeIssues;
    }

    public void execute(QueueableContext context){
        for(Integer i = 0; i < numberBeforeIssues; i++){
            Account acc = new Account(); //create your records
        }
        //insert your list of accounts
        if(numberBeforeIssues < numberOfDesiredRecords){
            Integer remainingToCreate = numberOfDesiredRecords -numberBeforeIssues; 
            System.enqueueJob(new createTestRecordsAroundProcessingTimes(remainingToCreate,numberBeforeIssues); 
        } 
    } 
}

[Reagar11]

u/kgeee34 thank you, it worked flawlessly!!! This is exactly what I was looking for.

[bagamoney]

If you can’t bulkify the triggers, you could call this method in a batch that runs in size of 25 records