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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

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.