Closed blairbenjamin closed 4 years ago
We're not using github much these days, so it's better to post on google groups (https://groups.google.com/forum/#!forum/yozonsesignforms) or email support directly.
That said, built-ins may vary in behavior for some items because when the email is sent, it may not have a concept of "user" anymore. Better is to build a document field to hold these values while the transaction is in process by the user. Then your email template can reference that more stable field value.
I'm using some built-in field values in email templates and getting inconsistent results. Sometimes it shows the value and other times it shows the field name. Below are screen shots from two emails sent as part of the same transaction using the same email template. On one it showed the value and on the other it instead rendered the field name. Why might this be?