---
asIndexPage: true
---

# DAX API

The DAX API enables Cube to connect to [Microsoft Power BI][ref-powerbi].
It derives its name from [data analysis expressions][link-dax], a query language
for Power BI and SQL Server Analysis Services.

Unlike the [SQL API][ref-sql-api], it provides a native experience and superior
support for Power BI features.

<InfoBox>

Available on [Enterprise and above plans](https://cube.dev/pricing).
Also requires the M [deployment tier](/product/administration/pricing#deployment-tiers).

</InfoBox>

Read below about the DAX API [configuration](#configuration),
[authentication](#authentication), and [using it](#using-dax-api-with-power-bi) with Power BI.

See the [DAX API reference][ref-ref-dax-api] for the list of supported DAX functions.

<YouTubeVideo
  url="https://www.youtube.com/embed/vgrFPOMuJJs"
  aspectRatio={8/5}
/>

## Configuration

<WarningBox>

Please contact the customer success team in Cube Cloud so we can guide you
through the configuration.

</WarningBox>

To enable or disable the DAX API on a specific deployment, go to <Btn>Settings</Btn>
in the Cube Cloud sidebar, then <Btn>Configuration</Btn>, and then toggle the
<Btn>Enable DAX API</Btn> option.

### Date hierarchies

By default, the DAX API exposes all [time dimensions][ref-time-dimensions] as _date
hierarchies_ in [Power BI][ref-power-bi]. You can set the <EnvVar>CUBEJS_DAX_CREATE_DATE_HIERARCHIES</EnvVar>
environment variable to `false` to disable this behavior.

Note that each date hierarchy will include additional columns, suffixed by `_year`,
`_quarter`, `_month`, `_day`. If the data model has other members with names that follow
this pattern (e.g., a time dimension named `date` and another dimension named `date_year`
in the same cube or view), that would cause a conflict.

## Authentication

The DAX API supports [Kerberos][ref-kerberos] and [NTLM][ref-ntlm] authentication
methods.

While NTLM can be used for testing purposes, we strongly recommend configuring
Kerberos for production environments.

## Data modeling

<InfoBox>

The DAX API only exposes [views][ref-views], not cubes.

</InfoBox>

## Cross-view filtering

By default, each view is exposed as a separate perspective in Power BI, so
visualizations from different views can't share the same filters. Cross-view
filtering lets you build dashboards that span multiple views and apply filters
consistently across visualizations, in both Live connection and DirectQuery
modes.

See [Cross-view filtering][ref-cross-view-filter] for details on how to enable
and use it.


[ref-powerbi]: /product/configuration/visualization-tools/powerbi
[ref-cross-view-filter]: /product/apis-integrations/dax-api/cross-view-filter
[link-dax]: https://learn.microsoft.com/en-us/dax/
[ref-sql-api]: /product/apis-integrations/sql-api
[ref-ref-dax-api]: /product/apis-integrations/dax-api/reference
[ref-views]: /product/data-modeling/concepts#views
[ref-time-dimensions]: /product/data-modeling/concepts#time-dimensions
[ref-kerberos]: /product/auth/methods/kerberos
[ref-ntlm]: /product/auth/methods/ntlm
[ref-power-bi]: /product/configuration/visualization-tools/powerbi