Field generation Lightning page assignment after deploy
Key Takeaway
Deploying and activating a Field Generation prompt template doesn't add the Einstein button to a field. You still assign the template to the field in Lightning App Builder, then save and activate the record page. For the Salesforce mobile app, "Dynamic Forms on Mobile" must also be enabled.
A Field Generation prompt template lets users fill one record field with an LLM-generated draft. They click an Einstein button on that field to get the draft. Moving this setup from sandbox to production means bringing three things into production correctly: the template, the Lightning record page that references it, and any flow the template uses.
How the template and the field connect
A Field Generation prompt template returns an LLM response to one specific field on a record. The template is tied to the Object and the Object Field that you choose when you create it.
Setup has two parts. You build the template in Prompt Builder. You configure the field in Lightning App Builder. On the record page, the Einstein button on the field triggers the assigned template and sends the response back to that field.
The two parts are separate, so an active template does nothing on a record page by itself. Users see the Einstein button only after the template is assigned to the field on a Lightning record page and that page is saved and activated. Deploying and activating the template in production doesn't put the button on any field.