Creating Parent and Child Salesforce Records in One Form Submission

A single form submission often needs to create more than one Salesforce record at once – an application that creates both a contact and a related case, or a donation that creates both an opportunity and a payment record, for example. Whether that is straightforward or painful depends entirely on how the underlying Salesforce object relationships are structured, which is exactly what Salesforce’s own documentation on object relationships covers.

Lookup vs. Master-Detail: Why the Distinction Matters for Forms

Salesforce supports two primary relationship types between objects:

• A lookup relationship, which loosely connects two records without controlling sharing or requiring the parent to exist first, allowing an object to have up to 25 lookup relationships.

• A master-detail relationship, which tightly couples a child record to its parent, meaning the child cannot exist without the parent, deleting the parent deletes the children, and an object can have at most two master-detail relationships.

A form that needs to create a parent and child record together needs to know which relationship type it is writing into, since the sequencing and required fields differ.

What This Looks Like in Practice

Creating a parent and child record from a single submission means the form platform has to create the parent record first, capture its resulting ID, and then create the child record referencing that ID, all within the same transaction so a failure partway through does not leave an orphaned or incomplete record. This matters most for common patterns: an application form that creates an applicant contact and an associated application record, or an intake form that creates a household and a related program engagement record.

Where This Gets Complicated

The complexity grows with the number of related objects a single form needs to touch. A donation form might need to create or update a contact, an opportunity, and a payment record, potentially across a master-detail relationship where the payment cannot exist without the opportunity. A form platform that only supports writing to a single Salesforce object per submission forces teams to either flatten the process into multiple manual steps or accept incomplete data relationships.

Where FormAssembly Fits

FormAssembly can create and update multiple related Salesforce records from a single form submission by chaining object steps in one connector, configuring parent objects first and linking child records to them by mapping the relationship field to the ID of the object created above, so parent records exist before their children reference them. Conditional logic can determine which related records get created based on what the respondent actually submits, and the entire operation is captured in FormAssembly’s audit trail. For Salesforce admins building forms that need to populate more than one connected object at once, that multi-object write capability is what keeps a single submission from turning into a multi-step manual data entry process afterward.