...
| Step | Notes | Result |
|---|---|---|
| Create formula fields for data | rather than {!relatedTo.ObjectA__r.Campaign__r.Account__r.Notes__c} I added the Notes field to Object B as a formula field so it was {!relatedTo.Notes__c} I did this for 3 fields |  No fields displayed |
| Send email immediately | The workflow was running after an hour | No fields displayed |
| Simplified the HTML Email | No fields displayed | |
| Added the IDs for all the objects into the email body |  ALL IDs Displayed!! | |
| Added the Names | If the Standard Fields of IDs display, do the standard fields of Names display? Because the field that is displaying from ObjectC is the Name field. | All Name fields displayed!! |
| Added the new fields without any HTML embellishment | Just replaced the name fields that did display with the fields I wanted to display. | No Custom fields displayed! |
| Wrapped the fields in the output tags | To try to see if there was anything to the non-answer in article 4. above. I also added Created Dates (standard fields) in output tags. |
|
| Changed to plaintextemailbody | Nope, no differentso it's not about HTML | |
| Changed the Contact lookup to be directly from Custom Object B | So instead of {!relatedTo.ObjectA__r.Contact.Notes__c} I had {!relatedTo.Contact__r.Notes__c} | Nope, so it's not about how far away the object is at all. |