Unexpected behaviour from 'Sort by column' on second report built on semantic model

[senref]

Hi all,  

I have a report built on a semantic model which includes a date table. 

[Year-Month] contains data like this: Dec 2025

[Year-Month Code] contains data like this: 202512

On my original report, the sort by column field appears as expected:

On the report I've built on top of the original model, however, [Year-Month] is still being sorted by [Year-Month].  

I've tried opening and closing bother versions, refreshing my original, republishing it, and then refreshing both it and the second report (even if the second is connected live) but I'm getting nowhere.  Is there anything I might be missing?  

Thanks for ny help.

[senref · Accepted solution]

OK - I think I've worked out where I've gone wrong here.  I just needed to ignore the greyed out data and change the sort axis on the vis.  Although the model view makes it look like [Year-Month] is being sorted by [Year-Month], if I sort the axis of the visual using this data by [Year-Month], it's in the order of [Year-Month Date] as I'd hoped.  

[senref]

Thanks for taking the time to respond @v-yangliu-msft .  On the original model, I've changed it.  It's not following through to the second report built on the same model, however.  I can't change it on that second report - I guess because that report is using a live connection to the first report's semantic model, the option is greyed out in the model view.  You can see that in the images above but my apologies for not making that at all clear.

[v-yangliu-msft]

Hi  @senref ,

As far as I know, the Sort by column of the calculation table in the model view defaults to sorting by its own columns, and you need to specify manually which columns to sort by.

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.