Forum Discussion
Hide blank values in matrix view
have a look at this file
https://1drv.ms/u/s!AjxUGXgGNzCEiV4mePewl33dzvil
with the way joins are set up you don't even have to specify in/out filter cause it comes from the visual fitler context
Community ChampionI'm not sure I get the complexity fully, but you could have a table like this one:
and use this code for SELECTEDVALUE to specify between In/Out
CALCULATE(SELECTEDVALUE(SDTable[Attempt]),SDTable[Direction]="In")
or you could do the Join table with SD with In/Out values only so it would always be filtered for single entry, but that may make model more complex
Yes so I have a alternative SDTable that does this;
But the resulting matrix still ends up looking like this:
How would I use a join SD table to filter the attempt_I, and attempt_O to their repective group, thus not showing any blanks?
- Stachu
have a look at this file
https://1drv.ms/u/s!AjxUGXgGNzCEiV4mePewl33dzvil
with the way joins are set up you don't even have to specify in/out filter cause it comes from the visual fitler contextThanks for that.
Unfortunatly it was the first stumbling block I hit. The measure is not doing what I intend from it.
Warm_AboveSD = SUMX(FILTER('Table','Table'[Warm]>=CALCULATE(SELECTEDVALUE(SDTable[Warm]))),'Table'[Warm])/60What its doing: A sum on all the WARM values, regardless of them being Inbound or Outbound, and then comparing to the selected SD value (warm inbound or warm outbound).
What im after: The selected value should only be compared to the SUM of WARM_Inbound values, hence my original measures for each inbound and outbound seperatly.
Is there anyway around this? Thanks
- Stachu
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
This does actually work, thank you very much Stachu