Asynchronous Apex - Batch Jobs - Explained | Chapter 99 | Salesforce Developer Masterclass

[@salesforcemakessense]

Code Snippet: public class BatchForOpportunities implements Database.Batchable, Database.AllowsCallouts, Database.Stateful { public Integer count = 0; public Database.QueryLocator start(Database.BatchableContext context){ System.debug('Start Method called'); String baseQuery = 'SELECT Id, Name, StageName FROM Opportunity '; String filterQuery = 'WHERE StageName = \'Perception Analysis\' AND CloseDate < LAST_N_DAYS:7'; String finalQuery = baseQuery + filterQuery; return Database.getQueryLocator(finalQuery); } public void execute(Database.BatchableContext context, List scope){ //do all the hard work here for(Opportunity opp : scope){ count++; System.debug(count); } } public void finish(Database.BatchableContext context){ //post processing logic here System.debug('Finish method called' + count); } }

[@haribabuk5162]

Batch Job makes Sense

[@salesforcemakessense]

Yay!

[@sumitB-h8t]

YES we are on the RIGHT TRACK..☺😅

[@salesforcemakessense]

Awesome!

[@ravigrover1923]

Start Method ran once Execute 10 times FInish also ran once

[@salesforcemakessense]

That's right.

[@thesalesforceseeker]

what about database.iterable ?

[@salesforcemakessense]

Iterables work similar to QueryLocator, just that there's no upper limit to the number of records that can be queried via an Iterator. However, CPU time limit does have an upper limit. But most of the times, queryLocator works fine and you can get used to it without doubt.