Print this page

Merge fields based on the Case Reason field fail to populate data

Knowledge Article Number 000212911
Description If you are generating email templates that have merge fields for the standard Case Reason field {!Case.Reason} and a custom Reason field the merge to the standard field may fail. The API names although not identical conflict in the application.  One quick way around this is to edit the custom "Reason" field and change the "API name" section to a name that doesn't contain the exact string "Reason".  Edit any templates using the custom Reason field to reflect the new merge field that will be generated after making this change.

promote demote