Forum Discussion

Linu's avatar
Linu
New Member
5 months ago
Solved

Power BI - Trendline exploration

i have a line chart with month-year and trAverage kw value in power bi i want show a trendline here and its slope and intersect value either on the graph or in card or kpi visual or in tooltip
Tips and Tricks
  • v-moharafi-msft's avatar
    v-moharafi-msft
    5 months ago

    Hi Linuu ,

     

    Yes, this approach can generally work in DirectQuery mode as well. Since the regression logic is being applied on aggregated results rather than raw row-level data, it is usually compatible with DirectQuery models.

     

    In some cases, errors can occur when the DAX logic becomes too complex for DirectQuery processing, especially when multiple table transformations or intermediate calculations are involved.

     

    A few workarounds that may help in this scenario are using a numeric sequence column instead of relying only on a text-based Month-Year field, keeping the calculations measure-based and as simple as possible, and building/testing the logic incrementally when introducing more advanced calculations.

     

    For more information, please refer to the official documentation:

    If possible, please share the exact DAX error message or the measure definition you are using so the issue can be narrowed down further.

    Hope this helps.

     

    Best Regards,
    Abdul Rafi

Linuu's avatar
Linuu
New Member
5 months ago

Hi Pankajnamekar ,

Thank you 

one thing i need o confirm here , is it direct query friendly ? as i am working on direct query as of now .

i tried writing dax but it is throwing me some errors .

 

v-moharafi-msft's avatar
v-moharafi-msft
Icon for Community Support rankCommunity Support
5 months ago

Hi Linuu ,

 

Yes, this approach can generally work in DirectQuery mode as well. Since the regression logic is being applied on aggregated results rather than raw row-level data, it is usually compatible with DirectQuery models.

 

In some cases, errors can occur when the DAX logic becomes too complex for DirectQuery processing, especially when multiple table transformations or intermediate calculations are involved.

 

A few workarounds that may help in this scenario are using a numeric sequence column instead of relying only on a text-based Month-Year field, keeping the calculations measure-based and as simple as possible, and building/testing the logic incrementally when introducing more advanced calculations.

 

For more information, please refer to the official documentation:

If possible, please share the exact DAX error message or the measure definition you are using so the issue can be narrowed down further.

Hope this helps.

 

Best Regards,
Abdul Rafi