Skip to main content

Populating merge field in email template while sending mail from apex.

Hi All,
You might have come across the issue of populating custom object info in email template dynamically. Suppose you have designed one email template having merge fields of contact object and one custom object. if you will send a mail from apex using singleEmailmessagApi then only contact merge field will be populated.This is an existing behavior of sfdc. How do we overcome this issue??

As we know if we will use setTemplateId method to set email template which we have already designed then we need to use setTargetObjectId method(Mandatory method ). 
setTargetObjectId only accept Contact,User and Lead id that is why  those object merge fields will be populated in email template. Now the question is how can we pass custom object id ?.

If we are setting contact id in setTargetObjectId  here then we can use another method called setWhatId,there we can pass custom object id.That means if we are sending mail to contact mail then we can pass custom object id so that all merge fields will be populated. 

Below is the snippet of code:-
Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage ();
mail.setTemplateId(template.id);
 mail.setOrgWideEmailAddressId(owemailaddress.Id);
mail.setTargetObjectId(contactid);
 mail.setWhatId(customobj.id);
Messaging.sendEmail(new Messaging.SingleEmailMessage[] { mail });

When we run this code we will get definitely exception, to overcome that make sure your custom object is enabled for activity history.There is check box when edit a object, we have to checked it. 

Then It will work for all user except portal, because portal user cant be owner of activity. For the portal user we have design email template in apex it self. Below is the post in this regards.



Comments

Popular posts from this blog

How to Create a Tooltip in Lightning Datatable ?

Imagine you have a datatable displaying a list of Contact records , and one of the columns shows the Account Name . The Account Name is a hyperlink that allows users to navigate to the Account record page. But what if users want to take a quick glance at some key Account fields —like Phone or Address—without navigating to the Account record? In Salesforce Classic, this was achieved using the Mini Page Layout feature from standard page. However, in Lightning Experience, we can implement a similar feature by adding a tooltip to the data table. Solution Overview: We’ll create a Lightning Web Component (LWC) that: Displays a data table with a clickable Account Name . Provides a tooltip that shows the Account's Phone and Address fields when users hover over the Account Name. Implementation Steps: 1. Data Preparation We need to retrieve the following fields for each Contact and its associated Account: Contact Fields : Name, Phone, Email Account Fields : Name, Phone, Billing Addre...

Lifecycle hooks in LWC

There are 3 phase of LWC component  1. Mounting  A. constructor, B. connnectedCallback C. render D. renderedCallback 2. UnMounting  A. disconnectedcallback 3. Error  A.errorcallback Note - render is not lifecycle hook, it is protected method of Lightning element class. Mounting Phase LWC Creation and Render Life cycle Constructor Method ·        This method called when component is instantiated and It flows from parent to child component. ·        Need to call Super() inside constructor method ·        Can’t access any component properties or child component because it’s not ready yet. ·        Host element can be accessed through “this. template” inside constructor method. ·        Don’t add any attributes to host inside constructor C   constructor (){          super (); //...

Style in LWC

 Following are the ways we can apply in CSS in LWC. 1. Inline CCS Inline CSS is not recommended approaches, it is take highest priority among all CSS. style="color:green;font-size:10px;" is inline CSS added to div < template >     < lightning-card title = "Inline CSS" >         < div >             < div style = "color:green;font-size:10px;" > This is inline Style div </ div >         </ div >     </ lightning-card > </ template >  2. External CSS style can be applied to an elements such as h1, p,div span etc. It can applied to class using "." notation. for example .user{} It can also be applied to pseudo class.  for example .user:hover{} Id locator is not being used in LWC to apply style To apply external css, need to create separate CSS file, file name should be exactly matched with component name. for example - If component name is ...