computed column filter

[Anonymous]

Hey guys!

I have two columns in my table that are named "stock" and "turn". Both columns can be filtered with two different filters. This works fine! 😉

Now I created a computed column that shows turn+12/stock. The problem is, that this computed column is not using the filters. So I always get the result, as there were no filters. Is there any possiblity to acchive what I need?

BR

[v-yuta-msft]

@Anonymous,

Have you solved your issue by now? If you have, could you please help mark the correct answer to finish the thread? Your contribution will be much appreciated.

Regards,

Jimmy Tao

[v-yuta-msft]

@Anonymous,

If you mean "computed column" is a calculate column, you should use measure instead because slicer chart is in report level while calculate column is in data model level so slicer will not affect calculate column. However, slicer can affect the result of a measure. If "computed column" is a measure, please share some sample data and the measure you are using for further analysis.

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Stachu]

I assume by the filter you mean slicers?
in order for the values to be affected by slicer they have to be in a measure not calculated column

here is a good article by Marco Russo explaining the difference between the two
https://www.sqlbi.com/articles/calculated-columns-and-measures-in-dax/

Choosing between calculated columns and measures

Even if they look similar, there is a big difference between calculated columns and measures. The value of a calculated column is computed during data refresh and uses the current row as a context; it does not depend on user interaction in the report. A measure operates on aggregations of data defined by the current context, which depends on the filter applied in the report – such as slicer, rows, and columns selection in a pivot table, or axes and filters applied to a chart.