Something Went Wrong Error when I try to Sort By Column

[motoray]

After installing the latest version of Power BI Desktop, I can no longer use Sort By Column. I get an odd error when I try. I also have an old version of Power BI Desktop for Report Server loaded and trying the same thing with the same column created from the same M code works fine. I've cleared the cache and reinstalled Power BI Desktop and still getting the error.

[motoray]

Things continue to work well for me after reimaging my VM and my work laptop. It only took a few days to get everything back to a place where I could be productive again. Sigh.

[BI_On_Rails]

I have the same issue. Even when I have just one row of data it says there are multiple values

[v-yohua-msft]

Hi, @motoray 

Make sure that the two columns involved in the Sort by Column action have the same level of granularity. This is a common requirement for sorting operations to work properly. For more details, you can refer to the documentation about sorting by columns:

Sort one column by another column in Power BI - Power BI | Microsoft Learn

Because the column was created from M code, there may be differences in how this code is interpreted or handled in the latest version of Power BI Desktop compared to the previous version. See if there are any features or actions in the M Code that may not be fully compatible or may appear different in the latest version.

Try creating a new, simplified Power BI file that replicates the Sort by Column scenario with minimal data and M-code. This can help you determine if the issue is related to a specific data model or a version of Power BI Desktop.

How to Get Your Question Answered Quickly 

Best Regards

Yongkang Hua

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

[motoray]

So I made a brand new table outside of PQ as shown below and got the same thing.

[motoray]

Will check this out and post back--great idea, BTW. Thanks.

[amitchandak]

@motoray , Hope you are using the latest version of Power BI Desktop Optimized for the report server.

Also, create a visual with both the columns as not summarized and check there is one-to-one mapping

This means one value in a column corresponds to one value in the sort column

[motoray]

I wasn't very clear in that first post-sorry abou that. We have an old report server and that's why I have PBI RS on my machine, but it's not what we use now. We're on the latest version (April 2024) of PBI Desktop and that's where my problem is. The Sort thing is for a date table we've been using for years and it's baked into a template we use. All I did was copy the already sorted Date Table query as a new query and load it and then tried to sort it exactly the same way it's sorted in the the other table...and I get that error.

[motoray]

I was able to download the Feb 2024 version of Power BI Desktop and it also worked as expected. I have a ticket with Microsoft but they are unable to reproduce the problem. Going to try another computer that someone else installed PBI Desktop April 2024 on later today to see if it's my two computers.

[dony]

The Sort by column selection still works on some columns, but not on date columns in the latest version. I have run into the same issue as you did. By the way, sorting by date columns still seems to work properly, but you cannot select them anymore in this version.

[motoray]

Got my virtual machine reimaged yesterday and after reinstalling Power BI Desktop (latest version), everything is working normally again. Once I have the VM going 100%, I'll be doing the same to my laptop. [sigh]

Microsoft support was 0% help and to make matters worse, I got an "empathetic" email from them that was 100% written by AI when I told them I wasn't looking forward to imaging computers. Hours and hours of my time and they spent 15 seconds to get AI to write a response. 

Grump grump.

[motoray]

Some news: I tested with a laptop that had been newly imaged and everything worked as it should. I'm in the process of getting my virtual machine reimaged to see whether that fixes things for me.