> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/sharinpix-form/create-child-records-with-form-sections.md).
# Create Child Records With Form Sections
## Overview
{% hint style="info" %}
In SharinPix Forms, every form response is directly linked to a **parent record**, which represents the object from which the form was initially launched. Beyond capturing information for the parent, the platform also provides the flexibility to create **child records** associated with it.
For example, if the parent record is an **Account**, the form can generate multiple **Contact** records linked to that account. This is achieved through form sections: each section can be mapped to a single child record. In cases where repeated sections are used, each repetition creates a new record—so if a user completes 10 repeated sections, 10 corresponding child records (e.g., Contacts) will be created.
This feature ensures that SharinPix Forms not only capture structured data but also seamlessly extend Salesforce’s relational model, making it easier to manage and organize information.
{% endhint %}
**Prerequisite:**
Before using this feature, ensure:
* You are using the most recent version of the SharinPix Package. Follow this document to [*upgrade the SharinPix package*](/faqs/how-to-update-sharinpix-package-from-the-appexchange.md)
* Users have the [***SharinPix Forms Admin*** *permission set*](/documentation/access-and-security/sharinpix-permission-sets.md) assigned.
## Getting Started
### How to configure sections on your Form Template to create child records for Template parent object.
The first step is to **create and configure a section** that will serve as the basis for generating the child record — or multiple records if it is set up as a repeated section.
Each section of the form includes an **Advanced** tab configuration in which you will find **Salesforce Record Mapping**.\
This configuration is divided into three key parts:
1. **Child Object API Name** – specifies the Salesforce object to be created.
2. **Lookup API Name** – defines the lookup field on the child object that links it to the form’s parent record.
3. **Formula Condition** – determines the criteria under which the child record(s) should be created.
Once the child object details have been configured, you can define how data from the form will populate Salesforce fields. Click the **“+”** icon to add new mappings, each representing a link between a **form field** and its corresponding **Salesforce field**. This ensures that when a form response is submitted, the captured data is accurately updated in the appropriate fields within the newly created child record.
A dropdown list containing all **Form Question API Names** from the current section will be available for selection. After choosing a question, enter the corresponding **Salesforce Field API Name** of the child record to which the selected question should be mapped.
As shown in the picture above, the "Inspection Checklist" section has been configured to create Fire Inspection records with 2 fields to input:
1. [Fire extinguishers present ?](https://documentation-dev-ed.develop.lightning.force.com/lightning/setup/ObjectManager/01IfJ000001bh2D/FieldsAndRelationships/00NfJ00000Ill2j/view)
2. [Last date fire extinguisher serviced](https://documentation-dev-ed.develop.lightning.force.com/lightning/setup/ObjectManager/01IfJ000001bh2D/FieldsAndRelationships/00NfJ00000IliGA/view)
On the **Inspection** record page, when a SharinPix Form is launched, completed, and submitted, a corresponding **Form Response** is created in Salesforce. If the *Create Records* condition evaluates to **true** , a new child record is automatically generated and linked to the **Inspection** record. This relationship can then be viewed under the **Fire Inspection** related list.
The corresponding values are then automatically populated in the newly created child record — **Fire Inspection** in this example as illustrated below.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sharinpix.com/documentation/sharinpix-form/create-child-records-with-form-sections.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.