Hi @aswinselva03 ,
The limitations of Direct Query in DAX functions are as follows:
- No built-in date hierarchy: Built-in date hierarchy isn't available when using DirectQuery. If there's a Date table available in the underlying source, as is common in many data warehouses, then the DAX Time Intelligence functions can be used as normal.
- Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can only refer to values of other columns of the same table, without the use of any aggregate functions. Additionally, the DAX scalar functions, such as
LEFT(), that are allowed, are limited to those functions that can be pushed to the underlying source. The functions vary depending upon the exact capabilities of the source. Functions that aren't supported aren't listed in autocomplete when authoring the DAX for a calculated column, and would result in an error if used.
- No support for parent-child DAX functions: When in DirectQuery mode, it's not possible to use the family of
DAX PATH() functions that generally handle Parent-Child structures, such as chart of accounts, or employee hierarchies.
- Calculated tables: You can use calculated tables in DirectQuery when using composite models.
For more information, please refer to:
Using DirectQuery in Power BI - Power BI | Microsoft Learn
Best regards,
Yadong Fang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
