Only in batch class finish method, We can call another batch class. If you will call another batch class from batch class execute and start method, then Salesforce will throw below runtime error.
System.AsyncException: Database.executeBatch cannot be called from a batch start, batch execute, or future method.
Here in below example there are two batch classes “Batch1” and “Batch2“.
I want to execute “Batch2” after finish the “Batch1“.
So, I’m calling “Batch2” class in “Batch1” finish method.
Batch1:
global class Batch1 implements Database.Batchable<Sobject>{
//Method to get the data to be proceesed
global database.Querylocator Start(Database.BatchableContext bc){
String query = 'Select Id, Name From Account Limit 1000';
return Database.getQueryLocator(query);
}
//Method to execute the batch
global void execute(Database.BatchableContext bc, Sobject[] scope){
for(Sobject s : scope){
Account a = (Account)s;
// TO DO
// add your logic
}
}
//Method to be called after the excute
global void finish(Database.BatchableContext bc){
//Add your start code for the other batch job here
Database.executeBatch(new Batch2());
}
}
Batch2:
global class Batch2 implements Database.Batchable<Sobject>{
//Method to get the data to be proceesed
global database.Querylocator start(Database.BatchableContext bc){
string query = 'Select Id, Name From Contact Limit 1000';
return Database.getQueryLocator(query);
}
//Method to execute the batch
global void execute(Database.BatchableContext bc, Sobject[] scope){
for(Sobject s : scope){
Contact c = (Contact)s;
// TO DO
// add your logic
}
}
//Method to be called after the excute
global void finish(Database.BatchableContext bc){
}
}
Salesforce introduced Named Credentials in the Spring’15 release.
Named credential specifies the URL of a callout endpoint and its required authentication parameters in one definition.
No need to handle Remote site settings of the Named credential callout URL.
Named credentials separate the URL from the authentication, making it easier to make changes to both the endpoint URL and authentication if needed.
It supports Basic Password authentication and OAuth 2.0 authentication protocols.
You can configured Named credentials to use an org-wide named principal or to use per-user authentication so that users can manage their own credentials.