Trigger Context Variables

-
Thought of writing a article around the context variables present in triggers.







Before Insert : 
Trigger.new would be available as new values are being inserted into the database
Trigger.old would not be available as fresh records are being inserted into the database
Trigger.newMap would not be available as the record id's are not generated in before insert event
Trigger.oldMap would not be available as the record id's are not generated in before insert event

After Insert : 
Trigger.new would be available as new values are being inserted into the database
Trigger.old would not be available as fresh records are being inserted into the database
Trigger.newMap would be available as the record id's are generated in after insert event
Trigger.oldMap would not be available as fresh records are being inserted into the database


Before Update : 
Trigger.new would be available containing the updated values
Trigger.old would be available containing the old values
Trigger.newMap would be available containing the updated values
Trigger.oldMap would be available containing the old values

 After Update : 
Trigger.new would be available containing the updated values
Trigger.old would be available containing the old values
Trigger.newMap would be available containing the updated values
Trigger.oldMap would be available containing the old values

After Delete :
Trigger.new would not be available as there is not update or insert performed
Trigger.old would be available containing the old values
Trigger.newMap would not be available as there is not update or insert performed
Trigger.oldMap would be available containing the old values

After Undelete :
Trigger.new would be available as records are restored from recycle bin
Trigger.old would not be available as this is similar to an insert event
Trigger.newMap would be available as records are restored from recycle bin
Trigger.oldMap would not be available as this is similar to an insert event

Comments

Post a Comment

Popular posts from this blog

Salesforce Lightning: Countdown timer

-
Image
Today we will have a look at how to create a lightning component for countdown timer which can be used on pages where an operation needs to be completed within a specific time period. Example, an online exam or a banking transaction which expires after a specific time period. The component contains a datetime field which represents the end time. Once the user selects the date and time and clicks on Start Timer button, the countdown timer will start. Below is the lightning component: CountdownTimer.cmp <aura:component implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId" access="global" >       <aura:attribute name="endTime" type="String"/>       <aura:attribute name="timeLeft" type="String"/>       <lightning:tile label="Time Left" class="slds-page-header">         {!v.timeLeft}     </lightning:tile...
Read more

Salesforce Hacks: System.LimitException: Too many queueable jobs added to the queue: 2

-
Queueable classes are great to use and provides a wide range of advantages when compared to future methods. But there are some undocumented limitations which you will come across if you are using Queueable classes extensively inside your batch classes. Lets take an example of badly written trigger on Account.  trigger AccountTrigger on Account (before insert) {     for(Account acc: Trigger.new){         Database.executeBatch(new CreateContactBatch(), 2);     } }   The above trigger calls a batch class for every account record that gets inserted in database. So if you insert N accounts in a single transaction via dataloader or anonymous block or through any other means, the trigger will execute the batch class N number of times. Below is the code for batch class: global class CreateContactBatch implements Database.Batchable<sObject> {          global Database.QueryLocator start(Database.Bat...
Read more

Building an Org Role Hierarchy component in LWC

-
Image
You might have observed that the role hierarchy which gets displayed in the org (Setup > Users > Roles) is still displayed using a VF component. Today, we will see how to create the same role hierarchy using LWC and Apex. LWC provides us with a component called lightning-tree which displays a nested tree. We will make use of this component to display the role hierarchy in a tree structure. In Apex, we will query all the user roles and form a JSON structure which will be fed to the lightning-tree component. Let's first see the LWC component - roleHierarchy: roleHierarchy.html <template> <div class="slds-p-around_medium lgc-bg"> <lightning-tree items={roles} header="Roles"> </lightning-tree> </div> </template> Here we have used the lightning-tree component which will display the data in a tree structure. The items attribute is of type Object which has nested i...
Read more