> For the complete documentation index, see [llms.txt](https://help.smallbuilder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smallbuilder.com/smallbuilder-lists/builder-setup-steps/datasource-setup/basic-datasource/add-and-configure-actions.md).
# Add and Configure Actions
**To integrate information retrieved from a DataSource into a List, field mapping actions are performed.** This process ensures accurate data merging by setting a common field as a Key between the DataSource and List records. Through this mapping, data from various sources can be effectively consolidated and managed.
{% hint style="info" %}
**What is Key?**
A common value used to merge data from the DataSource into the List.
{% endhint %}
{% hint style="info" %}
**Action Mapping Notes**
* **DataSource Field**
Displays the fields from the object specified in the DataSource. These fields provide the source data to be integrated into the List.
* **List Field**
Displays the fields from the object specified in the List Configurator. These fields serve as the destination for mapping the DataSource data.
* **Virtual Field**
Displays virtual columns created in the List. These fields allow for displaying additional data derived from the DataSource without modifying the original object structure.
{% endhint %}
***
### :small\_orange\_diamond: Steps to Add and Configure Actions
1\. In the **Actions** section, click the edit icon in the **Key** row.
Key Setting
2\. Select the DataSource field and the List field with common values, then click the **Save** button.
Key Setting Modal
3\. Verify that the configured **Key** is applied correctly, then click the **Add Action** button.
Edit Key Modal
4\. Select the DataSource field from which data will be retrieved and choose the List field or virtual field where the data will be saved, then click the **Save** button.
Add Action Modal
Datatable Setup
***
### :small\_orange\_diamond: Example
You want to display the price from the PricebookEntry object alongside a product list configured with Product2 in the List.
1. Search for and select PricebookEntry in the DataSource.
2. (Optional) In the Condition field, enter `IsActive = true` (similar to an SOQL WHERE clause).
3. To merge data for the matching PricebookEntry record:
1. Click the edit button in the **Key** row.
2. In the popup, configure the following, then save:
* **DataSource Field**: Product2Id
* **List Field**: Id
4. To display the **UnitPrice** from **PricebookEntry** in the List:
1. Create a **virtual column** (e.g., SBLS\_Virtual1) in the **Datatable Setup**.
2. Click the **Add Action** button.
3. In the popup, configure the following, then save:
* **DataSource Field**: UnitPrice
* **Virtual Column**: SBLS\_Virtual1
Basic DataSource Setup
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.smallbuilder.com/smallbuilder-lists/builder-setup-steps/datasource-setup/basic-datasource/add-and-configure-actions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
