---
title: "Link Management"
canonical: "https://docs.vaultspeed.com/space/VPD/3011248182/Link%20Management"
format: markdown
---
In the same way as you can change the order of the business keys inside a hub, you can also change the order of relationships within a link object.

In order to switch the order of relationships within Object-based Links (Many-to-Many Links, Hierarchical Links, Same-as Links, or Non-Historized Links), Link Management can be used.

### Managing Object-Based Links

When navigating to **Link Management**, you will see the list of object-based link objects and their corresponding sources.

**Link Management overview:**

![image](media://85a44aa3-82a7-499f-9d54-9f091d3a9861)

### Ordering Business Keys

To update the order, click **Ordering** and drag and drop the hubs around.

### Important: Business Key Ordering in Grouped Object-Based Links

When working with grouped Object-Based Links (e.g. Many-to-Many Links, Hierarchical Links, Same-as Links, or Non-Historized Links), the ordering of hubs (business keys) must be consistent across all source entities included in the group.

- The hub ordering in the resulting Object-Based Link (LND table) is determined based on the ordering of the hubs as defined for the **first entity** in the group.
- If the ordering differs between source entities, you may get incorrect column ordering or unexpected loading results.
- Always verify that the ordering of hubs is identical across all grouped sources before generating the release.

#### Example

In the example below, 4 object-based links are grouped from the source *Sales*. The order of the hubs defined for the first entity will drive the ordering for the resulting link structure:

**Mapping and order of the Business Keys of the Sources:**

![image-20250530-171844.png](media://6f87169d-cb9d-4349-843d-cff50f1ae529)

The resulting ordering is reflected in the generated LND structure, where the hub keys follow the defined order:

**Hub ordering in the generated LND structure:**

![image](media://1744083d-65be-43ce-812b-ea104d62b2e7)