Forum Discussion
Variance vs. Budget and Filters
No that should work. If you put a chart/table in your report with Project Number as axis and the measure as the value, it will calculate that measure for each Project Number as if that were a filter applied to the underlying data.
In more complex examples, there may be performance differences between calculated DAX columns and columns created in the query editor. The query editor generally will apply query folding and push the processing workload to the data source (where applicable), whereas the calculated DAX column happens within Power BI. DAX is way more flexible than the query editor, however, so my best advice is to do the ETL and mashing phase as much as possible in the query editor, but save the advanced pivoting and calculating for DAX.
thanks for the fast reply....
I also just changed the calculated column to a measure and it seemed to work.
YTD Variance = sum(CurYear[Actuals YTD]) - sum( CurYear[Budget YTD])
am i missing something as to why this might be bad?
thanks again
Alan
No that should work. If you put a chart/table in your report with Project Number as axis and the measure as the value, it will calculate that measure for each Project Number as if that were a filter applied to the underlying data.
In more complex examples, there may be performance differences between calculated DAX columns and columns created in the query editor. The query editor generally will apply query folding and push the processing workload to the data source (where applicable), whereas the calculated DAX column happens within Power BI. DAX is way more flexible than the query editor, however, so my best advice is to do the ETL and mashing phase as much as possible in the query editor, but save the advanced pivoting and calculating for DAX.