Expand SendBetterMail merge field functionality to support cross-object merge fields #1578
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building on, brace yourself, a 15 year old idea, I've extended the default SendBetterMail's email template functionality to also support cross-object fields, eliminating the need to manually insert the values or trash the data model with formula fields not needed elsewhere. The new feature keeps the default merge fields syntax with {{{field}}} and adds the cross-object syntax ###field### to prevent confusion and errors during the standard merging process.
All you need to know is the field path thats also used in SOQL queries, for instance if your Email templates source object is Case and you want to retrieve the associated accounts name, you insert the following into the template:
###Account.Name###
The code uses a single query to fetch all fields inserted into the template and automatically formats Date and Datetime fields in the running users default format.