Forum Discussion

Martin_Songstad's avatar
Martin_Songstad
Frequent Visitor
4 years ago

Reusing measure within object

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 measu...
johnt75's avatar
johnt75
Super User
4 years ago

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.

  • Martin_Songstad's avatar
    Martin_Songstad
    Frequent Visitor
    4 years ago

    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? 

    • johnt75's avatar
      johnt75
      Super User
      4 years ago

      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.