Sort by Column function influence measure result

[Anonymous]

Hi All.

Ok, so this is the strangest one, which I came across so far.

First, let me describe the part, which is understable.

I have a simple model, which contains one fact table and one dimension table with Account.

Then I've created a measure, which calculates sum of column value for account ZwykleKonto1. 

Measure = CALCULATE(sum(factFact[Value]), dimAccount[Account] = "ZwykleKonto1")

When I create a table visual with Account and Measure it looks like below, which is completly reasonable to me (measure filter overwrites context filter).

Now let's start with the mistic part. When I sort column Account by column Sorter, Measure starts to reflect 0 for Accounts with different Sorter value then 50 (which is value for ZwykleKonto1). I completly do not understand this behavious. Can I ask for explanation please?

Many Thanks, Kamil.

[Anonymous · Accepted solution]

After some research I found an article describing this behaviour.

https://blog.crossjoin.co.uk/2015/12/15/power-bi-desktop-sort-by-column-and-dax-calculations-that-us...

[amitchandak]

@Anonymous , Try like

Measure = CALCULATE(sum(factFact[Value]),filter( dimAccount, dimAccount[Account] = "ZwykleKonto1"))

refer

http://dataap.org/blog/2019/04/22/difference-between-calculate-with-and-without-filter-expression/