0

I have a roll up summary field that does not populate during an email alert.

I have tried setting a delay of one hour (allow the field to populate before the email alert fires out), but still the field does not populate in the email alert.

Checked FLS, among other things, no luck.

Has anyone else encountered this issue?

  • 1
    so you have a ROS field. You send an email alert, including the ROS field, and you see..what? You see nothing? You see a zero? You see the prior value? Is this a html email template or a visualforce email template? I've never had issue w/ this, though you can try to force recalculation of a ROS field which could perhaps help. Click edit - Force a mass recalculation of this field – gorav May 16 '17 at 2:07
  • @gorav No value, returns null. HTML Template, recalculation does not work. :( – All about the W May 16 '17 at 13:00
  • 1
    But it has a value when displayed on the page? How are you sure that the field has a value? – gorav May 16 '17 at 13:00
  • @gorav Thanks for your help. The detail page shows a value and my queries show a value. It is weird, perhaps because the field is from a managed package? – All about the W May 16 '17 at 13:06
  • 1
    Are you including the object name? I dont have a managed object + managed ROS field to test on, but testing on a managed ROS field on a standard object, you do need to include the object name so this does not work : {!npe01__LastDonationDate__c} and this does work : {!Account.npe01__LastDonationDate__c} – gorav May 16 '17 at 15:24
2

The Object name needs to be included in the email template merge field.

If you add a field using the email template generation UI, Salesforce does that automatically.

addFieldViaUI

If you copy the field's API name from the object details page, then you need to prepend the object API name manually.

objectDetailPage

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.