Is there a limitation merging dependent picklist values into a VF email template? I have a picklist (Case.Denial_Reason__c
) that is controlled by Case.Status
.
I can merge values such as status or text fields from Case just fine:
{!relatedTo.Case__r.Status}
{!relatedTo.Case__r.Customer_First_Name__c}
^ these both are merged and displayed ^
However, if I include:
{!relatedTo.Case__r.Denial_Reason__c}
It's not merged/displayed. I've triple checked FLS is correct for this field. I also included the controlling field with the dependent field, still nothing.
My next thought was to create a text formula field that simply channels the value from Denial_Reason__c
, i.e. TEXT(Denial_Reason__c)
:
{!relatedTo.Case__r.Temp_Formula_Denial_Reason__c}
but it's not merged. However, as soon as I change the formula field's value to be a static string such as "HELLO"
, the formula field is merged/displayed.
It seems as though anything that uses Case.Denial_Reason__c
as its true "source" can't be directly merged. I think I'll have to write the value in the relatedTo
object's trigger handler, unless I'm overlooking something here?