function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
viswsanathviswsanath 

Hi All, In which scenario we are using field update by using trigger . Can you please give me one example

Amit Chaudhary 8Amit Chaudhary 8
Please check below code:-

Example 1:-
trigger usernametorepresentative1 on employee__c (before update) 
{
	Set<Id> ownerIds = new Set<Id>();
	for(employee__C e1:trigger.new)
	{
		ownerIds.add(e1.ownerid);
	}
	Map<Id, User> userMap = new Map<Id, User>([ SELECT Id, Alias, FirstName, LastName FROM User where Id in :ownerIds]);
	for(Employee__c currEmp : Trigger.New)
	{
		if(userMap.containsKey(currEmp.OwnerId))
		{
			User usr = userMap.get(currEmp.OwnerId);
			currEmp.representative__c=usr.Alias;
			currEmp.representative__c=currEmp.ownerid;  
			currEmp.representative__c=usr.lastname;
			currEmp.representative__c=usr.firstname;
		}
	}
}

Example 2:- Please check below blog for more example and best pratice :-
http://amitsalesforce.blogspot.in/2015/06/trigger-best-practices-sample-trigger.html

1) One Trigger Per Object
A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts

2) Logic-less Triggers
If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org. 

3) Context-Specific Handler Methods
Create context-specific handler methods in Trigger handlers

4) Bulkify your Code
Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.

5) Avoid SOQL Queries or DML statements inside FOR Loops
An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception

6) Using Collections, Streamlining Queries, and Efficient For Loops
It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits

7) Querying Large Data Sets
The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore

8) Use @future Appropriately
It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found

9) Avoid Hardcoding IDs
When deploying Apex code between sandbox and production environments, or installing Force.com AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail

Please let us know if this will help you.

Thanks,
Amit Chaudhary
Shailendra Singh ParmarShailendra Singh Parmar
Hi Their,
Field update using trigger can be used when you are rolling up on parent object or you want to update parent record field based on update on child object record.

Thanks!
JAY_PJAY_P
Hey sir,
you have bulk of data and if you update all that object records you can use batch apex