Getting Started with TeamCity Tutorial | Learn in 1 Day with Ease

What Is Trigger In Salesforce?

A trigger is an Apex script that executes before or after specific data manipulation language (DML) events occur, such as before object records are inserted into the database, or after records have been deleted. TeamCity enable you to perform custom actions before or after changes to Salesforce records. A trigger is Apex code that executes before or after the following types of operations like insert, update, and delete.

There Are Two Types Of TeamCity:

• Before TeamCity: It is used to update or validate record values before saved to the database.
• After TeamCity: It is used to access values of the record that are stored in the database and use this value to make changes with other records.After trigger records are read-only.

Bulky Trigger

Salesforce Training For Administrators & Developers

All TeamCity are bulk TeamCity by default and can process multiple records at a time. You should always plan on processing more than one record at a time. Bulk TeamCity can handle both single record updates and bulk operations like:

• Data import
• com Bulk API calls
• Mass actions, such as record owner changes and deletes
• Recursive Apex methods and TeamCity that invoke bulk DML statements

A trigger is Apex code that executes before or after the following types of operations:

• insert
• update
• delete
• merge
• upsert
• undelete

When to use salesforce TeamCity

We should use TeamCity to perform tasks that can’t be done by using the point-and-click tools in the Salesforce user interface. For example, if validating a field value or updating a field on a record, use validation rules and workflow rules instead.

What is Trigger Syntax?

Trigger events in salesforce?

A trigger is a set of statement which can be executed on the following events. In above trigger events one or more of below events can be used with comma-separated.

Here is a list of trigger events in salesforce

• before insert
• before update
• before delete
• after insert
• after update
• after delete
• after undelete

Trigger Context Variables

Actions of Different Trigger Events

The following are lists of considerations about actions of different trigger events:

Insert Operation Before Insert:

• This trigger will be fried when a new record is going to be saved in the database.
• In before insert, trigger. New stores a new list of records which is going to be inserted.

Learn Hands-On Practical Salesforce Certification Course to Advance Your Career

Weekday / Weekend BatchesSee Batch Details

Example

After Insert

• After insert trigger will be fired after new record inserted successfully in database.
• New is going to hold a new record which is inserted into the database.
• After insert trigger is read only operation. We can do DML operations on new records which are inserted into the database.

Update Event There are two types of events

• Before update
• After Update

Trigger. Old and trigger. New are update events in salesforce.

Read: What Apex Email in Salesforce?

• New: Trigger. New is going to hold the list of records which going to be updated.
• Old: Trigger. Old is going to hold the set of old values which are going to be updated.

Before Update

It’s going to store the set record before updating to the database.

After update

• After the update trigger will be fired when the changes that we have made are saved to the database.
• In the after update trigger operation we can only read the data from trigger.
• If we want to make any changes we need to perform DML operation.

Example

Delete Event There are two events in delete

• Before Delete
• After Delete

Trigger. Old

This is going to hold the records which are going to be deleted. These records are read only by operation.

Before Delete example

After Undelete

• When we are undeleting records from the recycle bin after undeleting operation required.
• New is going to store the record which is undeleting from the recycle bin.

Trigger.newMap and Trigger.oldMap

Trigger.oldMap

A map of IDs to the old version of the sObject records. Note that this map is only available in update and delete TeamCity.

Trigger.newMap:

A map of IDs to the new version of the sObject records. Note that this map is only available in before update, after insert and after update TeamCity.

Types of Salesforce Triggers

Actually, there are no different types of TeamCity – but as the TeamCity are used before or after certain operations, they are considered to be of two types.

• Before TeamCity
• After TeamCity

Before TeamCity – These TeamCity run before the activity like updating or inserting a record into a database.

After TeamCity – These TeamCity are run for accessing the field values set by the system. They are also used to affect the changes in the records. For instance, after TeamCity are often used when dealing with audit tables and also when you handle asynchronous events with a queue. These after-TeamCity are considered read-only.

Syntax of a Trigger

The definition of a trigger starts with the trigger catchphrase and then followed by the trigger name.

The Trigger_Events can be a comma-separated list of any events like – before insert, before update, before delete, after insert, after delete, after update, or after undelete.

Considerations for implementation of Triggers in Salesforce

Certain considerations are to be kept in mind when implementing Salesforce TeamCity. Here are some of them.

• Before and after insert are fired by upsert TeamCity. Also, they fire the before and after update TeamCity whenever applicable.
• For the losing records, before and after delete are fired by the merge TeamCity and for the winning records before and after update TeamCity are considered.
• If the record has been undeleted and the trigger is performed after it, then it works only with certain specific objects.
• Till the end of the trigger, no records of field history are made. So, you cannot notice the history of current transactions when you ask for the field history in a trigger.
• The permissions of the current user are required to know the field history tracking. For instance, if a user doesn’t have a right to edit an object, but a trigger is activated still by the user to change an object with enabling the history tracking, then there will be no records of the history of the change.
• Asynchronous calls are to be made to avoid the blocking of the trigger process when waiting for the response of external service.

Trigger Context Variables

There are certain context variables which implicit the TeamCity – they help developers to access the run-time context.

• Trigger.isBefore – It gives true if this trigger ends before any record was spared.
• Trigger.isAfter – It mentions true value if this trigger ends after all records were spared.
• Trigger.isInsert – It avails true if it was fired for some insert operation, from the Apex, API, or the Salesforce User Interface.
• Trigger.isUpdate – It gives a true value when an update operation is done upon using this trigger.
• Trigger.isDelete – It gives genuine answer when one uses this trigger during any delete operations through Apex, API, or Salesforce user interface.
• Trigger.isUndelete – It gives a genuine things when one fires this trigger after recovering a record from the Recycle Bin.
• Trigger.new – new versions of the sObject records are showed with the help of it.
• Trigger.old – It provides a list of sObject records’ old versions. However, the list is only available in update and delete TeamCity.
• Trigger.newMap – It gives a map of IDs for the sObject records’ new versions. However, it is only found in before update, after update, after insert, and after undelete TeamCity.
• Trigger.oldMap – It gives a map of IDs to the sObject records’ old versions and is there in update and delete TeamCity.
• Trigger.oldMap – It gives a map of IDs to the sObject records’ old versions and is there in update and delete TeamCity.
• Trigger.size – It gives the total number of records (both old and new records) upon calling.

Having an idea on these TeamCity is very much important for developers and other Salesforce users to manage the appropriate functions accurately.

Summary

Apex TeamCity can help you to perform customized operations on a database. With this blog, we have learned a few facts about Trigger in Salesforce.