March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
I have simple dataset and my calculations are around specialty. So I always group results by specialty. When I tried to display the measures I created they show calculations correctly if the first column is Specialty. As soon as I add Provider ID field to the Rows section , measures give the total of all data not per Specialty
Here is the source file of the report:
https://drive.google.com/file/d/1WGDpRR0z-_n7aYzDHYF7IQRdmWtG_1Fg/view?usp=sharing
Am I doing something wrong 😞 ?
Thanks
Solved! Go to Solution.
@Anonymous wrote:@d_gosbell thank you for the reply. Your suggestion will be perfect if my client does not require the Provider ID to be included in the Matrix visual at the beginning before Specialty .
Oh, sorry - I think I misunderstood what you were expecting to see in the second table.
I believe that what you are actually seeing is an issue with ALLEXCEPT where it strips off even implied crossfilters. Probably a safer pattern to use is a combination of ALL and VALUES
eg
The SQLBI guys have a blog on this topic, the last few paragraphs summarize this issue
https://www.sqlbi.com/articles/using-allexcept-versus-all-and-values/
I think you are possibly over complicating things here, I'm not sure why you have added the ALLEXCEPT calls, but I think the calcs will work fine without them. When you have the specialty on the row it will naturally group by that column.
eg.
@d_gosbell thank you for the reply. Your suggestion will be perfect if my client does not require the Provider ID to be included in the Matrix visual at the beginning before Specialty .
@Anonymous wrote:@d_gosbell thank you for the reply. Your suggestion will be perfect if my client does not require the Provider ID to be included in the Matrix visual at the beginning before Specialty .
Oh, sorry - I think I misunderstood what you were expecting to see in the second table.
I believe that what you are actually seeing is an issue with ALLEXCEPT where it strips off even implied crossfilters. Probably a safer pattern to use is a combination of ALL and VALUES
eg
The SQLBI guys have a blog on this topic, the last few paragraphs summarize this issue
https://www.sqlbi.com/articles/using-allexcept-versus-all-and-values/
Thank you @d_gosbell for the formula. it works.. can you please explain to me what VALUE function does it this context?
Thank you again
@Anonymous wrote:Thank you @d_gosbell for the formula. it works.. can you please explain to me what VALUE function does it this context?
The VALUES function brings back the list of distinct specialities in the current filter context. So the ALL(Sheet1) strips all filters from the Sheet1 table and VALUES(Sheet1[Specialty]) then brings back just the current distinct set of Specialities.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
123 | |
85 | |
85 | |
70 | |
51 |
User | Count |
---|---|
205 | |
153 | |
97 | |
79 | |
69 |