Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
This should be super simple but I can't get it to work. I need to calculate the total check amount where if I filter for Ice Cream, I should get all of the item total for the checks that Ice Cream appeared on.
Here is an example of my data:
So if I have ice cream selected in a slicer, I need the total of checks 1 and 2, and not check 3.
Ideal output: 23 (totals of checks 1 and 2)
More details:
I pretty much need that second column to equal the third column when the second column is populated. The third column is calculate(sum(amount), all(item)) . The second column is just a sum of the amount.
As always all help is appreciated!
Solved! Go to Solution.
This measure gives you the expected output of 23.
I'm not clear that it'll work on your actual data though. Your screenshot has an additional field, discountjoin, that isn't explained where it fits in the model.
This measure gives you the expected output of 23.
I'm not clear that it'll work on your actual data though. Your screenshot has an additional field, discountjoin, that isn't explained where it fits in the model.
This is what the function ALLSELECTED is generally used for.
Your total with slicer filtering might look like this (or not depending on exactly what filters you want to include/exclude):
CALCULATE ( SUM ( Data[Amount] ), ALLSELECTED () )
Thanks for the input. I don't think this is what I need. I added allselected(item) to the sum and it returns the exact same thing as just a regular sum. I added some more details in the description. Maybe that clears things up
You didn't try quite what I suggested then. If you write ALLSELECTED ( Data[Item] ), then only the filter context on the [Item] column is reset to the slicer selection but the local filter context from e.g. [discountjoin] is still in place. Since I don't know what tables you have in your model, I suggested the broadest use of ALLSELECTED (without any table or column arguments). If this is too broad, you can modify it accordingly but I suspect applying on that single column may be too narrow.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
47 | |
26 | |
19 | |
14 | |
10 |
User | Count |
---|---|
58 | |
50 | |
44 | |
19 | |
19 |