How to work around the 100 callout limitation?



down voteaccepted
Create a batchable class, and do as many callouts as you need.
 The 100 callout limit applies only to a single transaction, but Batchable classes can create millions of transactions. 

You could do this:
global class Do2999Callouts implements Database.Batchable<Integer> {
    global Iterable<Integer> start(Database.BatchableContext context) {
        Integer[] values = new Integer[0];
        while(values.size() < 2999) values.add(values.size());
        return values;
    }
    global void execute(Database.BatchableContext context, Integer[] values) {
        // Do one callout for each integer in values
    }
    global void finish(Database.BatchableContext context) {
    }
}
You would call this code using:
Database.executeBatch(new Do2999Callouts(), 100);
Of course, this is only an arbitrary example. You could use smaller batch sizes, base them off of records, or do whatever else you need to. 

Comments

Post a Comment

Popular posts from this blog

Apex Trigger Framework in Salesforce with best practise

Image
                                                            Trigger framework is not just needed for having single object per trigger guidance but also helps in different other reasons. According to the trigger framework : 1) Create a single trigger for each object. 2) A handler class which will call Action or Apex Interface based Trigger Framework Implementation One Trigger -One Object Policy Framework Implementation Bulkified Code  Avoid SOQL Queries or DML statements inside FOR Loops  Using Collections, Streamlining Queries, and Efficient For Loops   No  Hardcoding IDs Types of Framework available : 1.Handler/Controller Framework 2.Lightweight Apex Trigger Framework (Source:  http://chrisaldridge.com/triggers/lightweight-apex-trigger-framework/ ) Handler Framewo...
Read more

Apex Classes as REST Web Services in Salesforce

Introduction to Apex REST Salesforce platform is amazing and its lets your create your own lightweight  REST API using Apex. You can use this REST API to access force.com data, by authenticating the caller/consumer of API using standard oAuth and return data format support JSON/XML, purely depends how you want return back the data A few useful bits of information related to these REST APIs: Use standard HTTP verbs: GET, POST, PUT, PATCH, DELETE, and HEAD. You can use either HTTP or HTTPS. Use standard security to authenticate your REST calls via OAuth 2.0. Serialize your data in either XML or JSON format. This is done by defining your Apex class with the  @RestResource  annotation to expose it as a REST resource. Similarly, add annotations to your methods to expose them through REST. For example, you can add the @HttpGet  annotation to your method to expose it as a REST resource that can be called by an HTTP  GET  request.  Ap...
Read more

Apex CPU Limit Error : after running into an Apex CPU limit error whether anything is committed to the database

In a batch that updates an object that then activates a trigger,  would it stop at the object level or at the trigger level or does it depend on  when the apex limit is hit? Any governor limit, including Apex CPU timeouts, reverts all changes to the database for the  entire  transaction. That means no records are created, updated, deleted, undeleted, merged, converted, etc. The  only  exception to this rule is that any logs that are enabled will be preserved (in Setup > Monitoring > Debug Logs).  In the case of a batch, if it occurs in the start method, the entire batch is aborted, while ' if it occurs during an execute function, only that single batch is aborted (but prior batches are already committed, and future batches may still successfully commit), and  in the finish method, a governor limit would prevent chaining calls, sending emails, etc.
Read more