Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

How the Filter definition of the metric can affect the final result.

Let's assume that I have the Products table in my model defined like this:

 

ProductIDUnitPriceUnitsInStockDiscontinued
11050TRUE
21530FALSE
32020TRUE
42510TRUE
5515FALSE

 

I have created two metrics :

 

Value1  = 

CALCULATE ( SUMX ( Products, Products[UnitPrice] * Products[UnitsInStock] ), FILTER ( Products, Products[Discontinued] = TRUE ) )

 

Value2 = 

CALCULATE ( SUMX ( Products, Products[UnitPrice] * Products[UnitsInStock] ), Products[Discontinued] = TRUE )

 

db2907_0-1686071686137.png

 

 

The only difference is the definition of the filter. I have evaluated the results in Power Desktop but I do not see any difference. This leads to my question: How could this definition affect the final result of the metric or when might this occur?

1 ACCEPTED SOLUTION
johnt75
Super User
Super User

The two measures are essentially identical, both are calculating the result for products which are discontinued. 

The definition for value2 is rewritten internally to be

Value2 =
CALCULATE (
    SUMX ( Products, Products[UnitPrice] * Products[UnitsInStock] ),
    FILTER ( ALL ( Products[Discontinued] ), Products[Discontinued] = TRUE )
)

The form of CALCULATE where you can specify a predicate as a filter rather than a table is merely syntax sugar, to make the code easier to read and write.

 

View solution in original post

1 REPLY 1
johnt75
Super User
Super User

The two measures are essentially identical, both are calculating the result for products which are discontinued. 

The definition for value2 is rewritten internally to be

Value2 =
CALCULATE (
    SUMX ( Products, Products[UnitPrice] * Products[UnitsInStock] ),
    FILTER ( ALL ( Products[Discontinued] ), Products[Discontinued] = TRUE )
)

The form of CALCULATE where you can specify a predicate as a filter rather than a table is merely syntax sugar, to make the code easier to read and write.

 

Helpful resources

Announcements
RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

Top Solution Authors