> 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/update-relationship.md).

# Update a relationship

When a relationship is on the wrong side, upstream when it should be downstream or the other way around, you do not delete and recreate it. You move it. You can also change a relationship's type without moving it.

## Move a relationship to the other side

### In Flow

1. Find the relationship row in the upstream or downstream column.
2. Use the row's **move control** or just drag and drop to send it to the opposite side. If more than one relationship type applies on the new side, pick one when prompted.

<figure><img src="/files/a6HX8e0nfjagK7DApJ9T" alt="" width="375"><figcaption></figcaption></figure>

### In Classic

1. Drag the connected element from its current connection point to the one on the other side.
2. Pick the relationship type for the new direction if you are prompted.

## Change the relationship type

If the side is right but the type is wrong, change just the type. In Flow, open the row's overflow menu and choose **Change relationship type**, then pick the new one. YouDesign Freelucy offers only the types your metamodel allows for that pair of records.

The update is staged until you [commit](/freelucy/work-in-the-app/commit-changes.md).

***

## What's next

* [Delete a relationship](/freelucy/work-in-the-app/delete-relationship.md)
* [Commit your changes](/freelucy/work-in-the-app/commit-changes.md)


---

# 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.ins-pi.com/freelucy/work-in-the-app/update-relationship.md?ask=<question>&goal=<endgoal>
```

`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.