> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/form-builder/creating-forms/additional-form-settings/conditions/conditional-values-of-fields/master-mapping.md).
# Master Mapping
We'll start by creating a master form first where we would map the values.
In the basic details under ***'**Apply master data settings',* turn on *'Use form submissions as master data for other forms'.*
The master form would have 3 select type fields **Purchase Type, Item Name** & **Item Price.**
Purchase Type
Gadgets, Stationery, Pantry
Price
Gadgets
Mouse, Keyboard, Monitor
450, 650, 1200
Stationery
Pen, A4 Sheets
200, 450
Pantry
Coffee, Muffins
200, 300
**Onc**e the options have been added go to **Settings > Conditions > Conditional value of fields** and map the data as per the table above.
Now we'll make the child form with similar fields.
Create another form with the select fields **Purchase Type, Item Name & Item Price** and a text field **Employee Name.**
Once we've made the form we'll pick master for the fields separately.
* Click the **settings** icon next to the select fields and open **Master data settings**.
* **Toggle on** *'I want to pick master for this field separately'.*
* Select the master form we made previously.
* ***'Select the master field from which value should be populate'***
Similarly select master for the remaining two fields **Item Name** & **Item Price**.
Last step of the process would be adding conditional settings in this form.
Just like the master form, we'll map **Purchase Type** with **Item Name** and **Item Name** with **Item Price**.
Here's how it would look like to the end user.
As per the data in the master form, options would populate the select fields.
---
# 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.senpiper.com/form-builder/creating-forms/additional-form-settings/conditions/conditional-values-of-fields/master-mapping.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.