> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/dashboards/power_bi/faq.md).

# FAQ

<details>

<summary>What is the integration URL and why does Coupler.io use it for Power BI?</summary>

Unlike spreadsheet destinations where Coupler.io writes directly to a file, Power BI pulls data from an external URL. Coupler.io generates a unique, secure JSON endpoint (the integration URL) for each data flow. Power BI connects to that URL via its **Get Data → Web** connector and reads the latest exported data. This means Coupler.io acts as the data layer between your source and Power BI.

</details>

<details>

<summary>What's the best write mode for Power BI dashboards?</summary>

* **Replace** is the right choice for most dashboards — it ensures Power BI always has a clean, current dataset without duplicates. Use this when your data flow pulls a full dataset each run (e.g., last 30 days of ad performance).
* **Append** is better if you want to accumulate historical records over time — for example, logging daily snapshots. Keep in mind that rows are never deleted in Append mode, so your dataset will grow with each run.

</details>

<details>

<summary>Can I combine data from multiple sources into one Power BI report?</summary>

Yes. You can add multiple sources to a single Coupler.io data flow and use **Join**, **Append**, or **Aggregate** transformations to combine them before sending to Power BI. Alternatively, you can create separate data flows for each source and combine the datasets inside Power BI using its own data modeling tools.

</details>

<details>

<summary>How do I keep my Power BI dashboard up to date automatically?</summary>

You need to set up refresh schedules in two places:

1. **Coupler.io** — schedule your data flow to run at your desired frequency (hourly, daily, weekly, etc.)
2. **Power BI Online** — after publishing your report, go to the semantic model, select **Schedule refresh**, and set a time that is *after* your Coupler.io run is expected to finish

Allow at least 10 minutes buffer for most sources, or 30+ minutes for high-volume sources like HubSpot or Pipedrive.

</details>

<details>

<summary>Can I use Coupler.io Power BI templates instead of building from scratch?</summary>

Yes — Coupler.io offers Power BI Template Apps for popular use cases (e.g., Facebook Ads, GA4). These give you a pre-built dashboard connected to your data. To use one, start from the template, connect your source accounts, run the data flow, and paste the generated integration URL into the Template App interface.

{% hint style="info" %}
See the [Power BI Template App setup guide](/destinations/categories/dashboards/power_bi/faq.md) for step-by-step instructions specific to templates.
{% endhint %}

</details>

<details>

<summary>Why does my integration URL show a 404 error in Power BI?</summary>

The integration URL is only active after your data flow has completed at least one successful run. If you paste the URL into Power BI before running the flow, Power BI will return a 404 error because there's no data at that endpoint yet. Run the data flow in Coupler.io first, then connect in Power BI.

{% hint style="info" %}
See the [Troubleshooting: Power BI destination](/destinations/categories/dashboards/power_bi/faq.md) article for a full list of connection errors and fixes.
{% endhint %}

</details>

<details>

<summary>Is there a row limit for data sent to Power BI?</summary>

Coupler.io's row limits depend on your plan, not the Power BI destination itself. If you're pulling large datasets (e.g., more than 100K rows from GA4), you may need a Business+ plan. Power BI Desktop and Power BI Pro have their own dataset size limits — check Microsoft's documentation for the most current limits on your Power BI plan.

</details>


---

# 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.coupler.io/destinations/categories/dashboards/power_bi/faq.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.
