AI-201 · Question #29
Universal Containers tests out a new Einstein Generative AI feature for its sales team to create personalized and contextualized emails for its customers. Sometimes, users find that the draft email co
The correct answer is A. The user does not have permission to access the fields.. When an Einstein Sales Email draft contains placeholders (e.g., {!Contact.Title}) instead of the actual field values, it means the system attempted to merge field data but could not retrieve it. The most common cause is that the running user lacks field-level security (FLS) permi
Question
Universal Containers tests out a new Einstein Generative AI feature for its sales team to create personalized and contextualized emails for its customers. Sometimes, users find that the draft email contains placeholders for attributes that could have been derived from the recipient's contact record. What is the most likely explanation for why the draft email shows these placeholders?
Options
- AThe user does not have permission to access the fields.
- BThe user's locale language is not supported by Prompt Builder.
- CThe user does not have Einstein Sales Emails permission assigned.
How the community answered
(28 responses)- A71% (20)
- B11% (3)
- C18% (5)
Explanation
When an Einstein Sales Email draft contains placeholders (e.g., {!Contact.Title}) instead of the actual field values, it means the system attempted to merge field data but could not retrieve it. The most common cause is that the running user lacks field-level security (FLS) permissions to read those specific fields on the contact record. Without read access, Salesforce cannot resolve the merge field and leaves the placeholder visible. A missing Einstein Sales Emails permission (C) would prevent the feature from working at all, not produce partial placeholders. Locale issues (B) affect language/formatting, not field data retrieval.
Topics
Community Discussion
No community discussion yet for this question.