Prompt Builder Limitations
Learn about the functional limitations of prompt templates that affect certain behaviors and outcomes.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Platform, or Einstein or Agentforce for Sales or Service add-on, or Agentforce Foundations |
Audit Trail Isn’t Supported
Creating or updating a prompt template isn’t tracked in the Setup Audit Trail.
New Custom Objects and Custom Fields Aren’t Immediately Available After Creation
When you create a custom object or custom field, it isn’t available for use in Prompt Builder immediately. To use a new custom object or field immediately, log out and log back in.
Records Without a Name Don’t Display in the Record Selector
Prompt templates with encrypted or missing name fields can’t be previewed. Their records are unavailable in the test record selector.
Supported Object Types
Salesforce supports many object or field suffixes to represent different types of data. Prompt Builder supports only these types of objects and fields as resources.
- UI API-supported objects. For a full list, see All Supported Objects.
Important The KnowledgeArticleVersion object is supported only for Flex Template types. - Standard objects (no suffix)
- Standard fields (no suffix)
- Custom objects (
__c) - Custom fields (
__c) - Histories (
__history) - Related lists (
__r)
Object Preview Limitations
You can’t preview objects with no Name field or objects whose Name field is encrypted.
Limitations for Field Generation Templates
You can’t use Field Generation prompt templates for rich text areas in knowledge entities
(__kav). To populate a knowledge entity’s rich text area
with a Prompt Builder template, use a Flex prompt template, Flow, or Apex.
Limitations for Flex Templates
You can’t import or export metadata from flex templates, including metadata related to flex templates. For example:
- Apex classes that reference flex templates
- Flows that reference flex templates
- Change sets to move flex-related artifacts between orgs
To delete flex templates that use flows or Apex classes, first remove any flows and Apex resources in all versions of the template. Second, delete any flows and Apex classes that reference the prompt template. Then delete the flex template.
Limitations for Einstein Search
If a prompt uses an Einstein Search retriever, the change sets don’t include the retriever or search index metadata. You must manually create the retriever in the destination org before deploying the retriever. This rule applies to change sets and Metadata API deployments.
