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
Hi!
For comparative analysis I would like to present a table like this:
My 4 column measures are fractions, with 4 slightly different but easily calculated numerator background measures, and a common but heavily calculated denominator background measure. So I would like this denominator background measure to calculate only once per segment, but suspect it happens 4 times, one time per measure - does it? Is there a more efficient way to actually reuse a calculation needed in several different measures shown simultaniously?
Hi @Martin_Songstad ,
Is your problem solved?? If so, Would you mind accept the helpful replies as solutions? Then we are able to close the thread. More people who have the same requirement will find the solution quickly and benefit here. Thank you.
Best Regards,
Community Support Team _ kalyj
It will be calculated for each measure for each segment and I don't believe there is a way around that using measures. The only way would be to store the calculation in a table, but that would not be affected by slicers or filters on the visuals. If the denominator is not affected by slicers and does not need to be dynamic then storing it in a table is definitely an option.
If it is affected by slicers, you still might be able to precompute the values for all possible combinations of slicer values, and store that in a table, if there is a reasonable number of combinations. It would increase data load time, when all the calculations would have to be performed, but that would be invisible to report users.
Thanks, @johnt75 !
I found that I can get a similar result by using a matrix table and just the Churn_rate_Total measure if i tweak the common background demoninator measure by adding ALL/REMOVEFILTERS(Churn_types):
CALCULATE(
SUM(.....),
REMOVEFILTERS(Churn_types)
)
The visual result is quite the same, and I would hope that the denominator now only calculates once per segment - or does it still calculate per shown value?
Certainly from a theoretical point of view you can see that caching would be an option, but I don't know enough about what happens in the background to be able to comment on whether caching would actually happen or not.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
22 | |
19 | |
17 | |
9 | |
5 |
User | Count |
---|---|
37 | |
29 | |
16 | |
14 | |
12 |