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

# Integration

Writing a value back changes the table in your database, but the Power BI semantic model keeps serving the data it imported earlier. This section covers closing that gap, so a reader sees their own change reflected in the report.

{% content-ref url="/pages/IPnFKuHGQrnnVbe7aMWf" %}
[Semantic model refreshing](https://docs.infotopics.com/features/power-bi-extension/integration/semantic-model-refreshing.md)
{% endcontent-ref %}

A refresh is requested, not awaited. WriteBackExtreme asks the Power BI service to start a refresh and the service accepts the request; how long it then takes is up to Power BI and the size of your model.

Refreshing a semantic model needs [Power BI SSO](https://docs.infotopics.com/features/power-bi-extension/authentication/power-bi-sso-setup.md), because the request is made with the reader's own Microsoft Entra token.


---

# 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/integration.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.
