> For the complete documentation index, see [llms.txt](https://help.taglo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.taglo.io/calculations/calculation-parts/variable-references/referencing-dimensions.md).

# Referencing Dimensions

## Auto Relationships

When you create a reference to a Variable that has [**Dimensions**](/dimensions/introduction-to-dimensions.md), Models needs to know which items within that Variable to reference when performing Calculations.

Most of the time, Models can automatically work out which items to reference.

For instance, in the example below, `Revenues by region and membership type` has the [**Calculation**](/calculations/introduction-to-calculations.md) `Gym members [Auto] * Revenue per member [Auto]`.

The `[Auto]` suffix to the Variable references indicates that Models will automatically deduce the correct relationships, based on Dimensions.

`Revenues by region and membership type` and `Gym members` both have two Dimensions: `Region` and `Membership Tier` - they vary both regionally and by gym package.

`Revenue per member` only has one Dimension, `Membership Tier`, as the price of the gym does not vary by region.

For each item of `Revenues by region and membership type`, Models will take the matching line from each of the reference Variables.

<figure><img src="/files/C9GDYUaOl2gBUhTokjxX" alt=""><figcaption><p>Example: Automatic Dimensions references. NOTE: Displayed values are rounded and will not produce calculated outputs shown</p></figcaption></figure>

## Custom relationships

We can configure the way that Dimensions are referenced.

For example, let's say we want to create a new Variable called `Revenue if everyone is Platinum`.

We use the same formula as in the example above (`Gym members * Revenue per member`), but this time we want the `Revenue per member` reference to only use the `Platinum` value.

To do this, we open the Calculation Part wizard for the `Revenue per member` Variable Reference, and navigate to the **Reference type** step, as shown below:

<figure><img src="/files/aAoYkPe6n0iS6BGCkWH7" alt="Screenshots showing how to create a custom relationships to a Variable using the Calculation Part editor wizard"><figcaption><p>Setting a Custom Dimension relationship</p></figcaption></figure>

In the item match dropdown, we select a **Custom** match <mark style="color:green;">**(1)**</mark>. A new step is displayed which allows us to customise the match for the `Membership Tier` Dimension. Here, we can specify that it should always link to the `Platinum` item <mark style="color:green;">**(2)**</mark>, rather than varying based on the source Variable's Dimension.

This results in the desired calculation, as shown below:

<figure><img src="/files/wJixsvgpljwrxlSYrFfN" alt=""><figcaption><p>Example: Custom Dimensions references. NOTE: Displayed values are rounded and will not produce calculated outputs shown</p></figcaption></figure>


---

# 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://help.taglo.io/calculations/calculation-parts/variable-references/referencing-dimensions.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.
