Model Performance

[Anonymous]

I am working with Microsoft Dynamics 365 CE data so I will use CE as my example, but the question is general enough that it can apply broadly.  I was rebuilding an old model the other day and am more focused on performance than I was when I built that original model.  My present model will be DirectQuery.

I wish to present to the user the sum of the estimatedvalue field from the Opportunity entity.  I need to be able to show open, won and lost slices of that sum.  In my old model, I created three separate measures (actually many more than that because we have several custom estimatedvalue fields for types of service/product and other characteristics like MTD, YTD, etc.):

     CALCULATE ( SUM ( estimatedvalue ), Status = open ) )

     CALCULATE ( SUM ( estimatedvalue ), Status = closed, State = Won ) )

     CALCULATE ( SUM ( estimatedvalue ), Status = closed, State = Lost ) )

It occured to me that I could have a single measure and add the filters to the visual objects themselves - or to a whole page if it made sense.  

My question:  Which scenario would provide the least drag on the performance - 3 measures, or 1 measure with filters on the visuals?  Or does it make no difference?

[v-frfei-msft]

Hi @Anonymous ,

Slicer is visualisation of a filter. So that makes no difference. In your scenario, one measure wilt filter will be better. As measure is a kind of calculation based on your selection in your filer / slicer. Measures are calculated at the time of your query, So The performance of one meaure with filter will be better here.