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

Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!

Reply
FritzVPL
Advocate II
Advocate II

Calculate function results change based on default sort order of a column

I need some help explaining this behavior. It caught me off guard and I can't seem to get my head around why its occuring.

 

See these two calculate metrics.

 

Test Filter = CALCULATE(sum('Test Fact Table'[Amount]),FILTER(Test_Dim_Table,Test_Dim_Table[Service Level]="Ground"))
 
Test No Filter = CALCULATE(sum('Test Fact Table'[Amount]),Test_Dim_Table[Service Level]="Ground")
 
FritzVPL_0-1721248331730.png

As expected, the "No Filter" test metric is repeating the value for ground on each service level.

 

However, if you change the default sort of service level to be off a different column, it will yield this result.

FritzVPL_1-1721249493296.png

 

Why does using the "Sort by Column" feature change the results of this calculation? Is this expected or a potential bug?

 

 

2 REPLIES 2
muhssamy
Resolver I
Resolver I

you are using "Sort by Column" not sorting from the grid itself ?

Correct, "Sort by column" sorting based on a different column on the same dimension table

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

Vote for your favorite vizzies from the Power BI World Championship submissions!

Sticker Challenge 2026 Carousel

Join our Community Sticker Challenge 2026

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

January Power BI Update Carousel

Power BI Monthly Update - January 2026

Check out the January 2026 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.