> 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/grid-layouts.md).

# Grid layouts

{% hint style="info" %}
Selecting the data structure for grid layouts can only be done in the dashboard extensions
{% endhint %}

### Option 1: A **KPI card per dimension member**, scenarios are **measures**

A **dimension** (e. g. Category) defines the number of KPI cards (one for every domain value).\
\
KPI scenarios (e. g. Actual or Budget) are stored in **measures** (e. g. Sales and Sales Budget).

<figure><img src="/files/dv6YTc3P1BtuSeU87eGt" alt=""><figcaption></figcaption></figure>

### Option 2: A **KPI card per dimension member**, scenarios are **dimension members**

A **dimension** (e. g. Category) defines the number of KPI cards (one for every domain value).\
\
KPI scenarios (e. g. Actual or Budget) are stored in a **dimension** (drag scenario dimension to detail).

<figure><img src="/files/hi3ctMUgprrjxfCpMPzF" alt=""><figcaption></figcaption></figure>

### Option 3: A **KPI card per (grouped) measure**, scenarios are **measures**

**Measure Names** define the number of KPI cards (one for every measure).\
\
KPI scenarios (e. g. Actual or Budget) are also stored in **measures** (e. g. Sales and Sales Budget) and can be grouped into one KPI card in the next step.

<figure><img src="/files/mUlANY8nNoMCxRnN3IjT" alt=""><figcaption></figcaption></figure>

### Option 4: A **KPI card per measure**, scenarios are **dimension members**

**Measure Names** define the number of KPI cards (one for every measure).\
\
KPI scenarios (e. g. Actual or Budget) are stored in a **dimension** (drag scenario dimension to detail).

<figure><img src="/files/lV2w31tmeFC8f2AZLtPP" alt=""><figcaption></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://docs.infotopics.com/powerkpis/getting-started/select-data-structure/grid-layouts.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.
