Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs-mintlify/docs/integrations/power-bi/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ hidden: true

Cube works with both [Power BI Desktop and Power BI Service][link-powerbi-desktop-vs-service].
If you're using Power BI Service, you need to set up an [on-premises data gateway][link-powerbi-gateway].
[Power BI Report Builder][link-powerbi-report-builder] is not supported.

<iframe
width="100%"
Expand Down Expand Up @@ -47,6 +48,7 @@ Cube supports the following authentication methods for Power BI:
| Power BI Desktop | [NTLM][ref-ntlm-desktop] | 🟡 Works well for testing purposes |
| Power BI Desktop | [Kerberos][ref-kerberos] | 🟢 Recommended for production |
| Power BI Service | [NTLM][ref-ntlm] + [Kerberos][ref-kerberos] | 🟢 Recommended for production.<br/>Requires [on-premises data gateway][ref-opdg] |
| Power BI Report Builder | — | 🔴 Not supported |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scope nit: this row lands in the Authentication methods table under "Connect to the DAX API", but the intro sentence at line 11 states Report Builder is unsupported for Cube generally (both DAX API and SQL API paths). Two small consequences:

  • A row with in an Authentication column is really answering "which applications are supported", not "which auth method to use" — a reader scanning for auth guidance gets a non-answer.
  • If the limitation is DAX-API-specific (i.e. Report Builder can still reach Cube over the SQL API as a Postgres source), line 11 overstates it; if it's global, the table row understates the reach by living in a DAX-only section.

Since line 11 already says it plainly, the table row is arguably redundant. If you want to keep both, worth making the intro sentence explicit about which API(s) it covers.


### Connection methods

Expand Down Expand Up @@ -85,6 +87,7 @@ so a sorted visual keeps its order except among groups that would otherwise tie.
[link-powerbi]: https://www.microsoft.com/en-gb/power-platform/products/power-bi/
[link-powerbi-desktop-vs-service]: https://learn.microsoft.com/en-us/power-bi/fundamentals/service-service-vs-desktop
[link-powerbi-gateway]: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem
[link-powerbi-report-builder]: https://learn.microsoft.com/en-us/power-bi/paginated-reports/report-builder-power-bi
[ref-count-distinct]: /reference/data-modeling/measures#type
[ref-dax-api]: /reference/core-data-apis/dax-api
[ref-integrations-apis]: /admin/connect-to-data/visualization-tools
Expand Down
Loading