Convert Prompt Templates To Related Salesforce Records Fully Declaratively — Example Step By Step…
Summary
This detailed guide shows how to fully declaratively convert prompt templates into related Salesforce records using the Agentforce Record Builder app. It addresses common challenges in automating record creation across related objects by walking through schema mapping, relationship types, field purpose definitions, hierarchy setup, versioning, and testing. Salesforce teams can learn to build flexible prompt-driven data generation flows that integrate with Generative AI, empowering dynamic record creation without code. The article also explains how to handle complex relationships and link existing files declaratively, valuable for admins and developers focused on automation and AI integration.
Takeaways
- Define schema mappings including sObjects, fields, and purpose descriptions declaratively.
- Use action buttons in the Agentforce app to manage schema versions and hierarchy safely.
- Configure lookup relationships correctly including parent, self, and child lookups.
- Create Flows that run prompt templates and process JSON output to upsert related records.
- Test generated records with sample data and uploaded files to validate schema mappings.
Convert Prompt Templates To Related Salesforce Records Fully Declaratively — Example Step By Step Instructions A set of examples with step by step instructions on how to use the Lightweight — Agentforce Record Builder App In a previous article called “ Convert Prompt Templates to Related Salesforce Records Fully Declaratively ” I wrote about a custom application that allows you to declaratively create records from a prompt template. This article is a step by step guide that requires you to read the previous article first to properly understand the background. If you want to go ahead and learn on the job, just follow the steps, but I would recommend understanding what you are doing. Creating a Schema Mapping 01) Decide the test Org First you need what Org you want to use for testing. The org will need to have all the sObjects and fields that you require for your (future) use case.