Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Hide blank values in matrix view

I have 2 tables containg call_IDs with a specific call direction (so table1 contains incoming, table 2 outgoing)   Table1: Call_ID Direction Attempt Cold Warm 1 In 101 81 29 2 In...
Need Help
Show and Tell
Tutorial Requests
Stachu's avatar
Stachu
Icon for Community Champion rankCommunity Champion
7 years ago

that's dpending on the visual filter context, and in all the screenshots you posted it was always unique to In/Out, never aggregated
I removed the division to make it more clear:

you can see that the code '>=' criteria only limited scope for the 'In', as that's what's filtered in the visual, even though the measure is the same for both

if you want this to be working on aggregated level as well then e.g. SUMX over SUMMARIZE could do the trick

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Sorry Stachu I dont think I understand this correctly. 

 

so if we take your measure from your screenshot;

 

Warm_AboveSD = SUMX(FILTER('Table','Table'[Warm]>=CALCULATE(SELECTEDVALUE(SDTable[Warm]))),'Table'[Warm])/60

Its telling the data to get every warm record in 'Table' where it is more than selected value, which is SD = 1, and Warm In which is either 62 or 26. So are you saying the measure is only going to compare Table[Warm] values that are of category 'In' to selected SD value 62 (thus Table[Warm] Out to selected sd value of 26) as this is how the tables are joined/filtered?  

 

So in sql I would normally do something like this: 

 

SELECT SUM(Warm) FROM FactHold WHERE Direction = 'Inbound' AND Warm >= 62 -- which is SD1 value for warm inbound

 

(Sorry also the aggregation is done at the end after the SUMX correctly compares each row value. My fault for the confusion earlier)

  • Stachu's avatar
    Stachu
    Icon for Community Champion rankCommunity Champion
    7 years ago

    the measure is always evaluated in the specific filter context that is coming from visuals - see more detailed explanation here
    https://www.sqlbi.com/articles/row-context-and-filter-context-in-dax/

     

    The filter context coming from the visual is
    for the left part of the table: Direction[Direction]= "In"
    for the right part of the  table: Direction[Direction]= "Out" 

    The filter context from Direction table propagates to both SDTable and the fact Table, which then gives different numbers