Prompt template change sets and metadata deployment
Key Takeaway
With default settings, a change set deploys every version of a prompt template, and the template arrives inactive in the target org even if it was active in the source org. Someone must activate it manually after deployment.
After you build a prompt template in a sandbox, you move it to production with a change set or with a metadata deployment. A prompt template has versions, so the key deployment decisions are which versions travel and whether they arrive active. Settings in Setup control both decisions for change sets. Flows and Einstein Search retrievers that a template uses need extra steps, and so does a custom LLM configuration.
How prompt templates move between orgs
Salesforce stores prompt templates as the GenAiPromptTemplate metadata type. You can move them between sandbox and production with these tools:
- Metadata API.
- Salesforce CLI. It syncs metadata between an org and a local DX project that you keep in a source repository such as GitHub.
- Change sets. When you build a change set, add all resources first, and then add dependencies.