A More In-Depth Exploration: Crafting An Apex Trigger

/ apex, Salesforce / By

Seeking a more comprehensive comprehension of our uncomplicated Apex trigger? Your search ends here!

Let’s revisit the code we crafted in the initial post:

trigger ForceForecasting on User (before insert) {
    for (User userInLoop : Trigger.new) {
        userInLoop.ForecastEnabled = true;
    }
}


Let’s begin by examining the pivotal line. I’ve distinguished this line with a profound green background to emphasize its significance

        userInLoop.ForecastEnabled = true;


If you only absorb one thing from this post, understand that this is the epicenter of all the magic. If your intention is to automatically fill the “Company” field for every new user, you can modify this line to:

 userInLoop.CompanyName = 'Google, Inc.';

Without altering any other lines of code, it would function seamlessly!

Now, let’s progress to the subsequent crucial lines of code. This comprises our loop:

    for (User userInLoop : Trigger.new) {
        ...
    }


If we were to express this code in plain language, it would essentially convey, “For each user within our trigger, execute all the actions enclosed within the brackets { }.” Every Salesforce trigger invariably includes one of these loops.

Lastly, let’s delve into the boilerplate code. Feel free to skip this part if you wish to conserve mental energy.

trigger ForceForecasting on User (before insert) {
    ...
}

Every Salesforce trigger is enveloped by this mundane code. Its sole purpose is to “commence” and “conclude” the trigger.


Definition of Utilized Variables


trigger – Every trigger must commence with this!

ForceForecasting – This is the designation we assigned to our trigger. We had the freedom to choose any name!

User – This is the title of the standard sObject in Salesforce. Including this in the initial code line instructs our trigger to respond to alterations in this object. The versatility extends to using custom objects as well – Salesforce offers remarkable flexibility!

before insert – This indicates that the trigger should activate before the User is inserted or created. Alternatively, we could have specified before update if that were our preference. A comprehensive list of operations is available here.

userInLoop – This variable serves as our representation for each distinct user as the loop progresses through all users in Trigger.new one by one. Remember, this variable only exists within the confines of the loop brackets! If desired, we could have configured it to modify any field on the User object by appending another field API name after the period. In programming etiquette, it’s customary to employ camelCase for variable names.

Trigger.new – This special Salesforce variable is a compilation of every User encompassed in our trigger. Generally, there will be only one User unless it’s a bulk insert, such as through Data Loader!

Related Posts