We Can't Sort the 'X' Column by "X'... error. No Duplicates, but There Used to Be... Bug??

[EMP]

Brought in a table, let's call it Table1. Tried to sort Level 3 column by Level 3 Order column. Received this error:

My bad BI, you are correct. Fixed the issue at the source and refreshed Table1. Duplicates gone. Tried to sort again, same error. This is where it gets interesting... I brought in the same query a second time, call it Table2. It's exactly the same thing as Table1 - only difference between Table1 & Table2 is that Table1 was brought in pre the fix and Table2 was brought in post. On Table2 I can sort Level 3 column by Level 3 Order column no problem - works perfectly. However, after refreshing and trying several other things to 'reset' Table1 I'm still unable to apply that same sort to Table1 - keep getting the same error. I've double checked that the duplicate issue was corrected on Table1 when I refreshed and it was... but it just keeps spitting out the error. Meanwhile Table2 sorts without issue. This feels like a bug...

Has anyone seen this before? Know how to fix it? I can just start over, use Table2 delete Table1 and move forward but I'm really curious if anyone has run into this before and knows how to fix Table1? 

Thanks,

EMP

[EMP · Accepted solution]

Rebooting my PC fixed the issue, so I'm guessing some kind of cache that was only reset when I rebooted <shrug> Thanks to all who commeneted with suggestions. 

[suparnababu8]

Hi @EMP 

Check the datatypes of the columns.

[lbendlin]

Another reason may be null values in the sort column.

[EMP]

No null values. To reiterate, I brought in a table that did have dups - my bad. Fixed it, tried to sort again and got the same error. Out of curisoity brought the exact same table in again and tried to sort - works perfectly. These tables are exactly the same (same source, same # of columns, nothing done to either one of them yet). The only difference is one was brought in pre me fixing the dups and the 2nd was brought in post me fixing the dups. It's like there's some kind of cache or something on 1 that makes it thinks the dups still exist even though they don't anymore.

[lbendlin]

Clear the query caches, maybe.

[EMP]

Assuming Google told me how to do that correctly (File-Options and Settings - Options , Under Global, select Data Load and select "clear cache" under "Data Cache Management Options" and select "clear cache" under "Q&A Cache Options" and select "clear cache" under "Folded Artifacts Cache Options") - that did not work.

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[EMP]

I've got a Pro license, I'll open a ticket. Thanks!