> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/powerkpis/getting-started/select-data-structure/tree-layouts.md).
# Tree layouts
### Option 1: **Pre-defined tree**
The parent-child relationship between KPIs is defined in two dimensions. Drag the **Metric** and the **Parent Metric** field to Dimensions. The parent of the main metric needs to be NULL.
Scenarios can be **dimension members** or **measures.**
### Option 2: **Build your own tree**
Use this option to build a free tree from different **measures**. The tree is configured in the extension in the next step.
Scenarios can be **dimension members** or **measures.**
### Option 3: Decomposition tree
Drag **dimensions** to Dimensions and drill into a measure to analyze contributors.
Scenarios can be **dimension members** or **measures.**
Set up a Decomposition Tree
---
# 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.infotopics.com/powerkpis/getting-started/select-data-structure/tree-layouts.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.
