Code Execution in Batch vs Trigger Mode

We often find ourselves in a situation where a specific code block that is stringed together in trigger which should not be executed in batch mode. The reason might be that batch execution might be triggering more number of triggers and hit any given governed limits. To achieve this in there is a method available in System class.

  1. !system.isBatch() – available for more information in this page
  2. Example Code Block: include this method in classes involved in trigger context to avoid executing in batch context.
if(!System.isBatch()) {           
    //call service class        

Extracting Field Level Security using the batch class

Most often Salesforce admins and developers tend to spend lot of time figuring out fields level security on multiple objects and fields and such process is time consuming in nature.

The following code is an attempt to extract FLS for a given object and for profile.

Step 1: Creation of batch class with Parameterized Constructor, SOQL query can be passed as string to the constructor.

//Batch Class For creating csv from query string and create file in predefined folder
global class BAT_FSCextract implements Database.Batchable<sObject>, Database.Stateful {
    public String query;  
    global String attachmentHeader;
    global List<String> csvRowValues = new List<String>();

    global BAT_FSCextract (String query){
        this.query = query;

    global Database.QueryLocator start(Database.BatchableContext BC){
        return Database.getQueryLocator(query);
    global void execute(Database.BatchableContext BC, List<sObject> scope){
        //Retrieved Records from the FieldPermissions (order: Name, Sobject Type, PermissionsRead, PermissionsEdit)
        for(FieldPermissions  currFieldPermissions : (List<FieldPermissions >) scope){
            String Field = currFieldPermissions.Field;
            String SObjectType = currFieldPermissions.SObjectType;
            Boolean PermissionsRead = currFieldPermissions.PermissionsRead;
            Boolean PermissionsEdit  = currFieldPermissions.PermissionsEdit;
            String rowStr = Field + ',' + SObjectType + ',' + PermissionsRead + ',' + PermissionsEdit;
    global void finish(Database.BatchableContext BC){
        List<Folder> folders = [SELECT Id, Name FROM Folder WHERE Name = 'FSC_log'];
            String documentName = 'FieldLevel Security-'+'MMM') +;
            attachmentHeader = 'FieldName, Object Name, Read, Edit\n';
            String csvFile = attachmentHeader + String.join(csvRowValues,'\n');
            // Insert the generated CSV file in Document object under "Setup Audit Trail Logs".
            Document doc = new Document(Name = documentName, Body = Blob.valueOf(csvFile), FolderId = folders[0].Id, Type = 'csv', ContentType='application/');
            insert doc;

Step 2. Construct SOQL query for the given profile and object, in this case it is System Admin profile and the Account object.

//String to be used in query
String queryToPass ='SELECT Field, SObjectType, PermissionsRead, PermissionsEdit FROM FieldPermissions WHERE parentId IN ( SELECT id FROM permissionset WHERE PermissionSet.Profile.Name = 'System Administrator' AND IsOwnedByProfile = true) AND SObjectType = 'Account' ORDER BY Field ASC';

Step 3. Execute the batch from any possible way, here code block is executed from anonymous execution block

//Call the batch
Id batchJobId = Database.executeBatch(new BAT_FSCextract(queryTopass));

There can be multiple extension this solution, for example ….
1. Run on schedule based or create UI elements to allow business users/sys admins to get ad hoc reports for FLS.
2. Schedule this every day and create deltas using server side applications.
which can look into the excel/csv files.
3. Merge files for different Objects and Different Profiles, same as use case mentioned in app exchange application but it needs considerable amount of efforts to get there.

JSON Class & JSON Parser

JSON is short for JavaScript Object Notation, and is a way to store information in an organized, easy-to-access manner. In a nutshell, it gives us a human-readable collection of data that we can access in a really logical manner. You can skimm about JSON in this article.

In real time we need to parse JSON data comes from external app or some time date needed to be presented on Vf pages using Java Script for complex data tables and insert into salesforce objects.For that we need to parse JSON data and insert them into database object as records or retrive Objact as JSOM string to Vf page.

Apex has two classes, JSON Class and JSONParser Class which can utilized in these scenarios.

JSON Parser

In real time we need to parse JSON data comes from external app and insert into salesforce objects.For that we need to parse JSON data and insert them into database object as records.For that we need to write the wrapper class with key names in json string we got and then by using json parser class we can do parsing as shown below.

In the following example i have a JSON string with lead data having firstname,lastname,company,city,state etc.

Page and Controller: 

<apex:form >
<div style="color:#FFFAF0;background-color:#808000;font-weight:bold;">
JSON String
<div style="color:#000080;background-color:#EEE8AA;width:100%;height:100px;">
<apex:pageBlock >
<apex:pageBlockButtons location="top">
<apex:commandButton value="Parse & Insert" action="{!parseJsonString}"/>
<apex:pageBlockTable value="{!lstlead}" var="le">
<apex:column headerValue="First Name" value="{!le.FirstName}"/>
<apex:column headerValue="Last Name" value="{!le.LastName}"/>
<apex:column headerValue="Company" value="{!le.Company}"/>
<apex:column headerValue="City" value="{!le.City}"/>
<apex:column headerValue="State" value="{!le.State}"/>
<apex:column headerValue="PostalCode" value="{!le.PostalCode}"/>
<apex:column headerValue="Phone" value="{!le.Phone}"/>
<apex:column headerValue="Lead Status" value="{!le.Status}"/>
public &nbsp;class Jsonstringparser {
public String jsonstring{get;set;}
public List<Lead> lstlead{get;set;}
public Jsonstringparser(){
jsonstring='[{"FirstName":"Balaji","LastName":"Malemarpuram","Company":"Oracle","City":"Hyderabad","State":"AP","PostalCode":500081,"Phone":9502026343,"Status":"Open - Not Contacted","Tags":[]},{"FirstName":"Sreevardhan","LastName":"Malemarpuram","Company":"Appshark","City":"Hyderabad","State":"AP","PostalCode":500081,"Phone":95055556343,"Status":"Open - Not Contacted","Tags":[]}]';
lstlead=new List<Lead>();
public void parseJsonString(){
JSONParser parser = JSON.createParser(jsonstring);
&nbsp;while (parser.nextToken() != null) {
&nbsp; if (parser.getCurrentToken() == JSONToken.START_ARRAY) {
&nbsp;  while (parser.nextToken() != null) {
&nbsp;   &nbsp;if (parser.getCurrentToken() == JSONToken.START_OBJECT) {
&nbsp;   &nbsp; Jsonparsercls le = (Jsonparsercls)parser.readValueAs(Jsonparsercls.class);
&nbsp;   &nbsp; Lead leadobj=new Lead();
&nbsp;   &nbsp; leadobj.FirstName=le.FirstName;
&nbsp;   &nbsp; leadobj.LastName=le.LastName;
&nbsp;   &nbsp; leadobj.Company=le.Company;
&nbsp;   &nbsp; leadobj.City=le.City;
&nbsp;   &nbsp; leadobj.State=le.State;
&nbsp;   &nbsp; leadobj.PostalCode=le.PostalCode;
&nbsp;   &nbsp; leadobj.Phone=le.Phone;
&nbsp;   &nbsp; leadobj.Status=le.Status;
&nbsp;   &nbsp; lstlead.add(leadobj);
&nbsp;   &nbsp;}
&nbsp;  }
&nbsp;  }
&nbsp;if(lstlead!=null && lstlead.size()>0)
&nbsp; insert lstlead;
public class Jsonparsercls{
public String FirstName{get;set;}
public String LastName{get;set;}
public String Company{get;set;}
public String City{get;set;}
public String State{get;set;}
public String PostalCode{get;set;}
public String Phone{get;set;}
public String Status{get;set;}


JSON Class

Contains methods for serializing Apex objects into JSON format and deserializing JSON content that was serialized using the serialize method in this class. Use the methods in the System.JSON class to perform round-trip JSON serialization and deserialization of Apex objects.


Apex Class

public class AccountJSON{
public String JSONtext {get;set;}
public Account VISacct {get;set;}
public String AccountSelected {get;set;}
public AccountJSON() { }
public void parseJson() {
String sAccName = 'Burlington Textiles Corp of America';
if (AccountSelected == null) {
AccountSelected = sAccName ;
String soql = 'SELECT Name,AccountNumber,site,AccountSource, AnnualRevenue,
BillingAddress, Fax,Phone, Website, TickerSymbol,
NumberofEmployees, Ownership, SIC FROM Account
WHERE name = :AccountSelected LIMIT 1';
Account acct = Database.Query(soql);
VISacct = acct ;
JSONtext = JSON.serialize(acct);
public List<SelectOption> getAccountList() {
List<SelectOption> AllAccountNames = new List<SelectOption>();
string tempaccount;
List<Account> Accounts = [SELECT Name FROM Account];
For (Account ar : Accounts ) {
tempaccount= (string) ar.get('Name');
AllAccountNames.add(new SelectOption(tempaccount,tempaccount));
return AllAccountNames ;

Vf Page

<pre class="wp-block-syntaxhighlighter-code"><apex:page docType="html-5.0" controller="AccountJSON" action="{!parseJson}" showHeader="false" sidebar="false" standardStylesheets="false" >
<script type="text/javascript">
function parseJson() {
var sJSON = document.getElementById("inJSON").value;
var obj = JSON.parse(sJSON );
document.getElementById("idtitle").innerHTML = obj.Name;
document.getElementById("idphone").innerHTML = obj.Phone ;
document.getElementById("idfax").innerHTML = obj.Fax;
document.getElementById("idwebsite").innerHTML = obj.Website;
document.getElementById("accname").innerHTML = obj.Name ;

document.getElementById("accountnumber").innerHTML = obj.AccountNumber;
document.getElementById("annualrevenue").innerHTML = obj.AnnualRevenue;
document.getElementById("ownership").innerHTML = obj.Ownership;
document.getElementById("numberofemployees").innerHTML = obj.NumberOfEmployees;
<html lang="en">
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="description" content=""/>
<meta name="author" content=""/>
<title>Account Details - Retrieve using JSON</title>
<link rel="stylesheet" href="" />
<link href="//" rel="stylesheet" />
<body >
<apex:form >
<div class="container">
<div class="row">
<div class="col-md-9">
<h4>Select Account</h4>

<apex:selectList value="{!AccountSelected}" size="1" id="cityddlb" styleClass="form-control" >
<apex:selectOptions value="{!AccountList}"/>
<apex:actionSupport event="onchange" reRender="strJSON" action="{!parseJson}"/>

<button type="button" onclick="parseJson()" styleClass="btn btn-primary" >
Get Account Details</button></div>

<div class="container">
<div class="row" >
<div class="col-md-9">
<div class="panel panel-primary">
<div class="panel-body bg-primary">
<h2 class="panel-title" id="idtitle">Account name will be populated
here via JSON</h2>
<div><small class="glyphicon glyphicon-th"></small> JSON below</div>

<apex:outputPanel id="strJSON">
<div> <input type="text" class="form-control" placeholder="Username" id="inJSON" value="{!JSONtext}" /></div>

<div class="row">
<div class="col-md-6">
<ul class="list-group">
<li class="list-group-item list-group-item-info"><strong>Account Details
<li class="list-group-item">Account Name: <span class="label label-primary" id="accname"></span></li>
<li class="list-group-item">Account Number: <span class="label label-primary" id="accountnumber"></span></li>
<li class="list-group-item">Annual Revenue: <span class="label label-success" id="annualrevenue"></span></li>
<li class="list-group-item">Ownership: <span class="label label-success" id="ownership"></span></li>
<li class="list-group-item">Number of Employees: <span class="label label-primary" id="numberofemployees"></span></li>
<div class="col-md-6">
<ul class="list-group">
<li class="list-group-item list-group-item-success"><strong>Important Information
<li class="list-group-item"><small class="glyphicon glyphicon-phone"></small>
Phone:<span class="badge alert-info" id="idphone"> </span></li>
<li class="list-group-item"><small class="glyphicon glyphicon-home"></small>
Fax: <span class="badge alert-info" id="idfax"></span></li>
<li class="list-group-item"><small class="glyphicon glyphicon-file"></small>
Website: <span class="badge alert-info pull-right" id="idwebsite" ></span></li>

<!-- /container -->
<div class="container">

<!-- /container -->
<!-- Bootstrap core JavaScript ================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<a href=""></a>
<a href="http://js/bootstrap.min.js">http://js/bootstrap.min.js</a>

Triggers and Order of Execution

Before Salesforce executes on event on the server, the client browser runs JavaScript validation check.

On the server, Salesforce:

  1. Loads the original record from the database or initializes the record for an upsert statement.
  2. Loads the new record field values from the request and overwrites the old values.

    If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:

    • Compliance with layout-specific rules
    • Required values at the layout level and field-definition level
    • Valid field formats
    • Maximum field length

    When the request comes from other sources, such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys. Prior to executing a trigger, Salesforce verifies that any custom foreign keys do not refer to the object itself.

    Salesforce runs user-defined validation rules if multiline items were created, such as quote line items and opportunity line items.

  3. Executes all before triggers.
  4. Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn’t run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
  5. Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as after triggers and workflow rules, are taken.
  6. Saves the record to the database, but doesn’t commit yet.
  7. Executes all after triggers.
  8. Executes assignment rules.
  9. Executes auto-response rules.
  10. Executes workflow rules.
  11. If there are workflow field updates, updates the record again.
  12. If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules, duplicate rules, and escalation rules are not run again.
  13. Executes processes.

    If there are workflow flow triggers, executes the flows.

    The Process Builder has superseded flow trigger workflow actions, formerly available in a pilot program. Organizations that are using flow trigger workflow actions can continue to create and edit them, but flow trigger workflow actions aren’t available for new organizations.

  14. Executes escalation rules.
  15. Executes entitlement rules.
  16. If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
  17. If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
  18. Executes Criteria Based Sharing evaluation.
  19. Commits all DML operations to the database.
  20. Executes post-commit logic, such as sending email.