All Ideas

Idea Details

Upvote Downvote

Post an Idea

35,810 Points

Open

Matt Brown

Cross Object Merge Fields in Email Template

Email & Email Templates

While it seems that you can use cross object merge fields in an email template, because they are exposed as merge field values, it does not work. Please allow the ability to use cross objects merge fields in email templates. Right now the only workaround is to use hidden formula fields on the parent object to copy the child object fields there and then build the template using those hidden formula fields. The disadvantage to this is that you are using up your custom field quota just to create an email template.

Merge Idea · Flag

Latest Comment from Salesforce

Kyle Skibbe - 5 months ago

Hi all - thank you so much for the use cases! Quick update: while this idea is certainly on our radar, we’ve been working to deliver a new drag and drop Email Template Builder in Winter ’21! (idea here: https://trailblazer.salesforce.com/ideaView?id=0873A000000CZPIQA4) and will focus next on the ability to use Lightning Email Templates in email alerts (per this idea: https://trailblazer.salesforce.com/ideaView?id=0873A000000EBHRQA4). These ideas lay the foundation for us to connect all the teams needed to bring cross object merge fields to life. Please stay tuned as we may ask you to help us prioritize our collective roadmaps in the January 202 IdeaExchange prioritization cycle. Thank you again for your input and feedback!

Flag

Comments ( 441 )

Sort By

Jessica Crowley - 5 days ago

I have a need for this same feature. I was using a Classic email template for a HTML email, but need to switch it to Lightning template so that users may edit the emails using this template. However, related object for the template is Opportunity, but I am unable to merge in the Account Name associated with the opportunity. This is possible using Classic templates, but not in Lightning.

Flag

John Sienkowski - 1 month ago

Absolutely needed!
- Flag
Martin Hofbauer - 1 month ago

Absolutely relevant feature.
- Flag
Victor Moura - 2 months ago

How is this not a feature yet?
- Flag
Jens Harnisch - 2 months ago

Needed!
- Flag

Dawn Ponce - 2 months ago

I echo @Amber Venzke and @Brian Kwong. We need this functionality and creating excess fields and processes requires too much unnecceary maintainence and as Brian said, is confusing when creating reports.
I hope this functionlity will be a high priority in your next cycle.

Flag

Bahiya LAHDID - 2 months ago

+1
- Flag
Christ Valentin - 3 months ago

Surprised this is not available yet
- Flag
Alan Ruan - 4 months ago

@Kyle Skibbe, I saw the new Email Template Builder, it's great. Looking forward to see cross object merge fields to be available. (or formula field support child objects)
- Flag

Bethany Payne - 4 months ago

I was trying to solve a complex use case and just discovered that this is not possible. How can an idea be so old with so many points? It doesn't make me feel better that it's going to be a possibility somewhere in the vague future if it's already 11 years old.

Flag

Gregory Ernest - 4 months ago

Kyle,

Looking forward to this! Need it for building good Macros to fill in complex email bodies for users.
- Flag

Kyle Skibbe - 5 months ago

Flag

Michael Herzog - 5 months ago

Trying to pull a quote line item field into an email template and being told that I cannot do this. Specifically, just trying to merge the quantity into an email template so I can confirm the quantity of an order automatically with a new customer. Thank you.

Flag

Jaime M - 5 months ago

Sorry for being off-topic, but bearing in mind that this development will not take place immediately, what do you think of this:
https://trailblazer.salesforce.com/ideaView?id=0874V000000lW9pQAE
- Flag

Jasmijn Tsang - 5 months ago

Use case example: Referring to a Contact's salutation and name from an email which is related to Case.

In Classic email templates, it was sufficient to put {!Contact.Salutation_Email__c} (our custom field for this) but on the Lightning Email Template, we cannot refer to any of the Case related Contact's fields it seems.