Forum Discussion
Efficiency problem
- 6 years ago
Anonymous ,
Create an additional table using dax below:
Account = DISTINCT('Table'[Account])Then create slicer based on the new 'Account' table and create measure using dax below:
Result = VAR SelectedAccount = SELECTEDVALUE(Account[Account]) RETURN CALCULATE(SUM('Table'[Sum]), FILTER(ALL('Account'), 'Account'[Account] <> SelectedAccount))You can also refer to pbix attached.
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.
- Anonymous6 years agoNot applicable
Hi,
Thank you, elegant and efficient! I need to further look into this, as I really don't understand why the relationships are required in the background and if I would like to add a second column to the filter and the table (for example account name) it does break down.
But these are issues that should be solved by me now that I have the core.
Thank you!
- Anonymous6 years agoNot applicable
Hi,
Actually this has a small issue with it. If i slice multiple items, it shows the other side of the journal entry, yes, but it also shows the accounts i have selected. So the inverse-selection doesnt work with multiple items. Is there a fix for this?
Thank you!