> 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/features/power-bi-extension/getting-started.md).

# Getting started

Before people can write data back from a Power BI report, you add the WriteBackExtreme visual to the report, map at least the column that identifies a row, point the visual at your WriteBackExtreme server, and configure a schema.

{% content-ref url="/pages/iHRXFkYfS01jQaRW8Whg" %}
[Add the extension to your Power BI report](https://docs.infotopics.com/features/power-bi-extension/getting-started/add-the-extension-to-your-power-bi-report.md)
{% endcontent-ref %}

## The four data wells

Only the first is required.

| Data well              | What to put in it                                                                                                                                                                                                              |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Primary key**        | The column that uniquely identifies a row. The visual does not go past its start screen until this is filled.                                                                                                                  |
| **User**               | A measure holding the current user, when you identify people by username rather than SSO. See [Username setup](https://docs.infotopics.com/features/power-bi-extension/authentication/username-setup.md). Only one field fits. |
| **Default values**     | Columns whose values prefill fields in the form.                                                                                                                                                                               |
| **Dynamic population** | Columns that fill dropdown options from the report.                                                                                                                                                                            |

The visual's start screen repeats this as a **Data mapping guidance** table, with a tick next to each well you have filled, so you can see at a glance what is still missing. Until a primary key is there, **Start configuring** is replaced by:

> Primary key is required before you can continue.

{% hint style="info" %}
The visual reads up to 10 000 rows from the report. Beyond that, filter the page down before expecting every record to be reachable.
{% endhint %}

## Pointing it at your server

A Tableau extension knows where its server is, because it was loaded from it. A Power BI visual comes from AppSource or a file, so it has to be told. On first run it asks, under **WriteBackExtreme Setup** / **Connect your environment.**

You can also set it later in the format pane, under **Settings** > **Connection** > **Backend URL**.


---

# 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/features/power-bi-extension/getting-started.md?ask=<question>&goal=<user_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.
