In Salesforce, email alerts sent via Workflow Rules may fail to populate certain merge fields — specifically picklist fields such as the Product field — in the email template body. The fields appear correctly when using "Send Test and Verify Merge Fields" in the email template, and when sending via the Emails related list on a Case.
This issue occurs when a managed package installs a field on the Case object with the same base API name as an existing custom field, causing the Salesforce merge engine to reference the wrong field value.
When reviewing the org, check if a managed package is installed with a field whose base API name matches your custom field. For example:
Apttus_Config2 is a third-party managed package. When the namespace prefix is removed, both fields share the base API name Product__c. This causes the Salesforce merge engine to become confused and return the value for the managed package field instead of the custom field.
Choose one of the following options to resolve the merge field conflict:
000386817

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.