Cannot Order Table Error Message

[tecumseh]

Hi all,

Refresh is completing, but with errors.
The error messages is pretty generic and not very helpfule what is causing the error.
What can I do to troubleshoot to get rid of the errors?

Thanks,

w

[v-sgandrathi]

Hi @tecumseh,

We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.

If you need any further assistance, feel free to reach out.

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-sgandrathi]

Hi @tecumseh,

Thank you @cengizhanarslan  and @tayloramy  for your answers to the query.

Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help. 

Thank you.

[tecumseh · Accepted solution]

@cengizhanarslan @tayloramy 

Thanks for your replies. Here is what I did to resolve.

Error Message Numbers

Those numbers in the error message are the id's for the table and columns respectively.
I translated those id's to names by using INFO.VIEW

INFO.VIEW.TABLES()
INFO.VIEW.COLUMNS()

Using this I was able to narrow down that the problem was my Date Table and specifically MonthName_1 (A single character for the Month Name) and the Sort Column " Sort Year Month"

I entereed the DAX for the Calculated Column in Google Gemini. Gemini recommended a few changew which I tried. No Improvement - still get an error message. 4-5 rounds of this, always an error message.

Gemini finally recommended a complete refresh and rename the the single character column to something else. The cache is stuck.

That solved it.

Lessons:

1. If you get a handful of id's that do not make sense, translate them to the table names and column names

2. Refresh and change names of columns - the cache is stuck.

Thanks

w

[cengizhanarslan]

A column in your model is configured to sort by another column, but new data has introduced rows where a single display value maps to more than one sort value — violating the one-to-one requirement. Power BI detects this conflict at refresh time and throws the warning because it can no longer determine a consistent sort order for that column. The refresh still completes, but the visual sort order for the affected column may be incorrect or unpredictable until the conflict in the data is resolved.

[tayloramy]

Hi @tecumseh, 

This error message is telling you that a table is trying to be ordered in a non deterministic way, though it is odd that it is not telling you the table name (unless you have a table called 12587). 

Are there any tables that you are defining a sort order on in your model?