> For the complete documentation index, see [llms.txt](https://docs.sprinkledata.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinkledata.com/product/analysing-your-data/data-models/hierarchies.md).

# Hierarchies

Hierarchies can be added to **define a relationship between fields** where the values of one can be controlled by the other in a **nested way**.

Hierarchies allow you to use the **drill feature** on Reports and Dashboards allowing you to drill down and drill up on your data to perform interactive analysis and explore trends.

Once a hierarchy has been added to the model, it will be available in the hierarchies section (located on the left-most pane under the custom section) of the report created from this model. Hierarchies can also be added to the reports directly.

If your visualizations have been configured with hierarchies, the drill option will be available to you. There are two kinds of drill actions you can perform:

1. You can perform **drills all at once**. For example, if you are on country-level sales data and you drill down, you go to state-level data.
2. You may **select a data point and then drill down**. For example, on state-level sales data, you click on the cell where the state is equal to Karnataka (India), and then click on drill down.\
   \
   \
   \ <br>

<br>


---

# 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.sprinkledata.com/product/analysing-your-data/data-models/hierarchies.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.