> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/plan/infobridge/how-tos/query-transformations/append.md).
# Append Queries
Use **Append Query** to combine rows from multiple queries into a single query. Append queries when the source tables have the same column structure and compatible data types.
### Example scenario
To illustrate how **Append Query** works, imagine a scenario where you store employee bonus data separately for the HR, IT, and Sales departments.
The following table shows sample employee bonus data for the HR department.
| Department | Bonus percentage | Role |
| ---------- | ---------------- | ---------------------- |
| HR | 20% | HR Manager |
| HR | 15% | Recruiter |
| HR | 12% | Training & Development |
| HR | 8% | Payroll Coordinator |
The following table shows employee bonus data for the IT department.
| Department | Bonus percentage | Role |
| ---------- | ---------------- | ---------------------- |
| IT | 20% | Software Engineer |
| IT | 15% | Network Administrator |
| IT | 12% | Database Administrator |
The following table shows employee bonus data for the Sales department.
| Department | Bonus percentage | Role |
| ---------- | ---------------- | ---------------------------- |
| Sales | 5% | Sales Manager |
| Sales | 12% | Digital Marketing Specialist |
Append the department data to create an organization-level view of employee bonuses. The following table shows the appended data from all departments.
| Department | Bonus percentage | Role |
| ---------- | ---------------- | ---------------------------- |
| HR | 20% | HR Manager |
| HR | 15% | Recruiter |
| HR | 12% | Training & Development |
| HR | 8% | Payroll Coordinator |
| IT | 20% | Software Engineer |
| IT | 15% | Network Administrator |
| IT | 12% | Database Administrator |
| Sales | 5% | Sales Manager |
| Sales | 12% | Digital Marketing Specialist |
### Append queries
The following example shows how to append regional sales queries into a single query.
1. Open the bridge that contains the queries you want to append.
In this example, the bridge contains sales queries for Australia, Canada, France, United Kingdom, and the United States.
2. On the **Data** tab, select **Append Query**.
3. In the **Append Query** dialog, expand the **Source** field and select the queries that you want to append.
Select only the queries that contain the data you want to combine. For example, if a bridge contains sales and budget queries, select only the relevant sales queries.
4. Verify the queries that appear in the **Source** field.
5. Select **Apply**.
After the append operation completes, Infobridge creates a new query that contains the combined rows from the selected queries. Infobridge lists the source queries under **Source Name**, and the append operation appears in the **Performed Steps** pane.
Next, continue transforming the appended query as needed or write the data to a destination.
---
# 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.fabricplan.com/documentation/plan/infobridge/how-tos/query-transformations/append.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.