Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 years ago
Solved

FILTER vs CALCULATETABLE

I'm about to lose some serious street cred, but so be it... :)   I use FILTER( ) all the time and CALCULATETABLE( ) almost never.  Is there some time I *should* be using CALCULATETABLE?  What is th...
Need Help
Tutorial Requests
  • mattbrice's avatar
    mattbrice
    9 years ago
    Anonymous wrote:

    What if I remove CALCULATETABLE from the language.  What do we lose?

    CALCULATETABLE triggers context transition whereas FILTER does not.  Andy by itself, FILTER creates a row context whereas CALCULATETABLE does not.  But other than these, it is a question for Marco if he is lurking around out there...potential performance issues per his article I referenced would be one thing I would think...

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Ya, of course I went to see what marcorusso had to say! :)   But ... somehow it didn't help me.  At least from a pure functionality perspective -- as that seems to do more w/ performance.

 

And yet, I'm not convinced they are functionally equivalent.

v-jiascu-msft's avatar
v-jiascu-msft
Icon for Microsoft Employee rankMicrosoft Employee
9 years ago

Hi Anonymous

 

"Filter" can generate a row context while "Calculatetable" can't. In the example below, the formulas are very similar. Both work but bring us different results. Hope this would help.

 

Filter_NumOfCities =
COUNTROWS ( FILTER ( 'Table15', 'Table15'[CITY] = EARLIER ( Table15[CITY] ) ) )
Calculatetable_NumOfCities =
COUNTROWS (
    CALCULATETABLE ( 'Table15', 'Table15'[CITY] = EARLIER ( 'Table15'[CITY] ) )
)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Best Regards!

Dale