Salesforce Fact #627 | Passing list of Sobject across batch apex

Suppose we need to pass List<Sobject> records from one batch apex to another. We can call the 2nd batch from finish method of the 1st one and pass the list of records.

In this example, we are creating 5 account records in batch1 and then passing the records to batch2 from the finish method of 1st batch. In this case, we need to use the Iterable<SObject> type and the 1st batch needs to implement Database.Stateful interface to retain the value.

Attached are the screenshots.





Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more