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
sonali  vermasonali verma 

Optimize apex code using Map

Hi
I have a requirement.When we update  Account record, the related Description field of contact object should get updated automatically.
 
I am able to achieve the requirement but I want to know whether we can use Map to optimize the code further.
Pls help me.
 
public class Account_ContactDescription
{
     public static void Update_Description(Set<Id> accountIds)
    {
                    
           list<Account> accountsWithContacts =[select Id,Name, (select Id,FirstName,LastName from Contacts) from Account  where Id IN : accountIds];
           
           list<Contact> contactsToUpdate=new list<Contact>();
           
           for(Account a:accountsWithContacts)   //loop through all queries 
          {
                 for(Contact convals:a.Contacts)
                {
                        convals.Description=convals.FirstName+' '+convals.LastName;
                         
                        contactsToUpdate.add(convals);
               }
           }
           
           update contactsToUpdate;
    }
}

trigger trg_Description on Account (before Update)
{
   
    Account_ContactDescription c=new Account_ContactDescription();
     
    Map<Id,Account> amap = new Map<Id,Account>([select Id from Account]);
     
    Set<Id> accountIds = amap.KeySet();
     
    c.Update_Description(accountIds);
          
}

Thanks
sonali

 
Best Answer chosen by sonali verma
Pankaj_GanwaniPankaj_Ganwani
Hi,

You can achieve this functionality with Process Builder too. However, if you want to accomplish this using trigger you can use below mentioned code. I have optimized your code a bit:
 
public class Account_ContactDescription
{
     public static void Update_Description(Set<Id> accountIds)
    {
           
		   for(Contact objContact : [select firstName, LastName, Id from Contact where AccountId In : accountIds])
		   {
				contactsToUpdate.add(new Contact(id = objContact.Id, Description = objContact.FirstName+' '+objContact.LastName));
		   }
		   
           update contactsToUpdate;
    }
}

trigger trg_Description on Account (after Update)
{
   
    Account_ContactDescription c=new Account_ContactDescription();
     
    c.Update_Description(Trigger.newMap.keyset());
          
}

 

All Answers

Pankaj_GanwaniPankaj_Ganwani
Hi,

You can achieve this functionality with Process Builder too. However, if you want to accomplish this using trigger you can use below mentioned code. I have optimized your code a bit:
 
public class Account_ContactDescription
{
     public static void Update_Description(Set<Id> accountIds)
    {
           
		   for(Contact objContact : [select firstName, LastName, Id from Contact where AccountId In : accountIds])
		   {
				contactsToUpdate.add(new Contact(id = objContact.Id, Description = objContact.FirstName+' '+objContact.LastName));
		   }
		   
           update contactsToUpdate;
    }
}

trigger trg_Description on Account (after Update)
{
   
    Account_ContactDescription c=new Account_ContactDescription();
     
    c.Update_Description(Trigger.newMap.keyset());
          
}

 
This was selected as the best answer
sonali  vermasonali verma
Hi pankaj
I ran ur code and it works.
I checked the code with  before Udpate   event  and it works.
Can u pls clarify whether  "before Update"  or  "after Update" is an better option in this case?

Thanks
sonali verma
Pankaj_GanwaniPankaj_Ganwani
This would be on after update since you are performing the DML on other object. Before events are only used when we have to perform updations on the same object the trigger is acting on or need to show some error message to prevent the record from being committed to database.
Pankaj_GanwaniPankaj_Ganwani
If this solves your issue and aforementioned explanation clarifies your doubt, please close this thread by marking the best answer so others can also refer the same.