> 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/getting-started-with-the-vizextension.md).
# Getting started with the VizExtension
To quickly get started with PowerKPIs, download the free PowerKPIs viz extension from the Tableau Extension Gallery or your local viz extension .trex file.
Then follow these steps:
**For Grid Layouts**
1. Add your measures to **Measure**
2. Add a **Date** field to **Date**
3. Add a KPI dimension (e.g. *Segment*) to **Cards**
4. *(Optional)* Add a **Scenario** field to **Scenario**
5. Click ⚙️ and configure your PowerKPIs
6. Have fun!
***
**For Tree Layouts**
1. Add your measures to **Measure**
2. Add a **Date** field to **Date**
3. For recursive data (parent-child), add a KPI and Parent KPI field to **Cards**
4. For categorical data, add hierarchy fields to **Cards** and define the hierarchy in the extension
5. Click ⚙️ and configure your PowerKPIs
6. Have fun!
Congratulations on your first PowerKPIs project 🎉!
Optionally add more measures to the Measure Values shelf or a dimension to break down a measure dimensionally.
---
# 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/getting-started-with-the-vizextension.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.
