Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

BUG: DAX Variable is storing the filter conditions and impacting another query using that Variable

For a Actual vs Forecasting table, I am trying to extract the Maximum Date of Actuals, or even the Minimum Date of Forecasting to then do a cumulative value.

 

The intention is to have two lines that do not overlap. So for the last 3 months, the Actuals Cumulative would not be a straight line (due to 0 rolling sum), and would cut off at the Maximum Actual Date.

 

I have done this formula multiple times, storing that date in a Variable, to then reference in a Calculate formula to sum all values less than that date.

 

The Variable for the date is storing the filters used of Type = Actuals, or Forecast and any other conditions I may apply, when I have never had this before since the Variable is meant to be independant and return a scalar or table result.

 

Can an answer be provided as to why the Variable is sotring filter conditions, rather than applying the scalar value of date that I need?
 

Status: Investigating
Comments
Anonymous
Not applicable

Hi @candidBeing ,

 

 

Based on the above information, It's a reproducible issue. Due to the new reply policy, I would suggest opening a Support Ticket.

If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

 

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

 

Best Regards,
Community Support Team _ Caitlyn