> 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.md). # Power BI extension WriteBackExtreme ships as a Power BI custom visual. Drop it on a report page, point it at your WriteBackExtreme server, and the people reading the report can write data back into your database from inside Power BI — add records, correct values, keep a side table, leave comments. It is the same WriteBackExtreme you know from Tableau, running inside a Power BI visual. The modules, the forms, the permissions, the audit trail and the management console are all shared. What differs is everything that depends on a Tableau *dashboard* rather than a single visual. {% content-ref url="/pages/JyaDuuppX4hY1jid1WnB" %} [Getting started](/features/power-bi-extension/getting-started.md) {% endcontent-ref %} {% content-ref url="/pages/Y1mzMrjxjZe7jXyrKzmY" %} [Authentication](/features/power-bi-extension/authentication.md) {% endcontent-ref %} {% content-ref url="/pages/bmtKL4gE3WGPVAqBnua6" %} [Integration](/features/power-bi-extension/integration.md) {% endcontent-ref %} ## What works All four modules run in Power BI: [Data Add](/features/tableau-extension/end-user/add-data.md), [Data Correction](/features/tableau-extension/end-user/data-correction.md), [Data Helper](/features/tableau-extension/end-user/data-helper.md) and [Collaboration](/features/tableau-extension/end-user/collaboration.md). So do the cross-module features — search, bulk edit, import and export, duplicate, and history with rollback — and the whole form builder, including conditional visibility, validation, defaults and cascading dropdowns. Authentication is the most developed part: [Power BI SSO](/features/power-bi-extension/authentication/power-bi-sso-setup.md) signs people in with their Microsoft Entra account, and can create WriteBackExtreme users for them on the way in. ## What is different from Tableau Read this list before you plan a report around a Tableau design. These are not settings you can turn on. | In Tableau | In Power BI | | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The extension can open as a popup or a floating object | Neither exists. The visual sits on the canvas like any other. | | Tabs let one instance serve several schemas | One visual, one schema. Use several visuals for several schemas. | | Several worksheets can feed one instance | One visual's own data. There is only one worksheet, and it is the visual. | | Tableau parameters can drive the form | Not available. | | Datasources can be refreshed by name | A semantic model is refreshed through the Power BI API instead, and only the one you select. See [Semantic model refreshing](/features/power-bi-extension/integration/semantic-model-refreshing.md). | | Selecting nothing usually means *all marks* | Selecting nothing means **nothing is selected**. | That last row catches people out. In Tableau an empty selection commonly shows every record; in Power BI, when no other visual is cross-filtering, there is no selection at all. Data Correction in particular will have nothing to show until something filters the visual. Re-selecting the datapoints behind a record — which Tableau does when you open a record for editing — only works for columns that are in the visual's own data wells. ## What you need * **Power BI Desktop or the Power BI service**, with the WriteBackExtreme visual added to the report. * **A WriteBackExtreme server** your readers can reach, and its URL. The visual asks for it on first run. * **A column that identifies a row**, in the **Primary key** data well. The visual will not go any further without it. * **A licence that covers Power BI.** Without it the visual shows **Product not licensed!** [Getting started](/features/power-bi-extension/getting-started.md) walks through the setup. --- # 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.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.