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

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. 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
Fabric Data Days is here Carousel

Fabric Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

May Power BI Update Carousel

Power BI Monthly Update - May 2026

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

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.