If you set up and test AI Engine in a sandbox first, the finished configuration does not travel with a change set or a metadata deployment. AI Engine stores its settings as records in the package's custom objects, so they have to be entered again or copied as data.
What is stored where#
| What you configured | Stored in |
|---|---|
| Org Profile (provider, models, playbook, PII, branding, Meeting Prep objects) | AI Engine Profile |
| Agent Objects (objects, fields, child objects, digest settings) | AI Agent Config |
| Prompt Templates | AI EnginePrompt |
| Data sources of prompt templates | AI Prompt Data Source (each record points to its prompt template) |
| AI Scoring settings | AI Scoring Config |
| PDF Templates | AI PDF Template |
Steps#
- Install the package in production and assign the permission sets. See Install the package and Assign permission sets.
- Recreate the External Credential and Named Credential in production and enter the API key again. Credentials and keys are never copied between orgs. Use the same Named Credential name as in the sandbox, or update the Org Profile afterwards. See Connect your AI provider.
- Copy the configuration. For a small setup, re-entering it in the Ai Agent Admin Setup tab is quickest. For a larger one, export the records listed above from the sandbox and import them into production with Data Loader or a similar tool:
- Import prompt templates before their data sources, and map each data source's prompt template lookup to the new production record.
- Record IDs differ between orgs; do not copy ID values into text fields.
- Check the Org Profile in production: the Named Credential name, the models and, for Azure OpenAI, the deployment names.
- Activate the scoring schedule again. A scheduled scoring job is not copied with the settings; open AI Scoring and click ▶ Activate.
- Place the components on your Lightning pages and utility bar, or deploy those pages with your usual metadata process. See Add components to pages.
- Activate the license for the production org. A license key works only in the org it was issued for. See License and trial.
- Run a first test before rolling out. See Run a first test.