> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/freelucy/work-in-the-app/create-multiple.md).
# Create multiple relationships at once
Map several records to the same primary element in one gesture.
When you need to attach several records to the same primary element, you do not have to add them one by one. Select them all in the Data Hub and add them as a batch.
## Step by step
1. Open the [Data Hub](/freelucy/work-in-the-app/data-hub.md).
2. Hold **Ctrl** or **Cmd** and click each record you want to map. Selected records highlight.
3. Add the whole selection at once, either way:
* **Click to add.** Choose **Add to Upstream** or **Add to Downstream** for the selection.
* **Drag to add.** Drag the selection onto a valid drop target in your current view.
4. If the records support more than one relationship type, YouDesign Freelucy prompts you. You can:
* **Pick a type for each record**, or
* **Apply one type to the whole batch.**
Every record in the selection is staged on the chosen side, ready to commit.
***
## What's next
* [Commit your changes](/freelucy/work-in-the-app/commit-changes.md)
* [Update a relationship](/freelucy/work-in-the-app/update-relationship.md) if you need to fix one
---
# 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://docs.ins-pi.com/freelucy/work-in-the-app/create-multiple.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.
