Update completed with notifications.

[emme1010]

Hi, I'm getting this message on the service power bi , but the report looks fine on the desktop.

but I can't find table 165694

can you help me?

[lbendlin]

Run a DMV query to find out which table has ID 165694. 

[v-sshirivolu]

Hi @emme1010 ,
In Microsoft Power BI Service the message “Update completed with notifications” indicates that the refresh has completed, and you can review the refresh history in the Service for more details about any messages returned during the process. Since your report is working as expected, this suggests the refresh was successful.

From the message shown in your screenshot, it appears related to a column being sorted by another column where the mapping may not be one-to-one, which can lead to such warnings. You can review the Sort by Column configuration in your model to ensure the sorting column has a valid mapping.

References:
https://learn.microsoft.com/power-bi/connect-data/refresh-data
https://learn.microsoft.com/power-bi/create-reports/desktop-sort-by-column

[v-sshirivolu]

Hi @emme1010 ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[v-sshirivolu]

Hi @emme1010 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

[andrewsommer]

This is a "Sort By Column" conflict. You have a column set to sort by another column, but the relationship between those two columns is not one-to-one, meaning one value in the sort column maps to multiple values in the other column.

How to fix it

1. Find the offending Sort By Column setting
• In Power BI Desktop, go to the Data view
• Select the table/column in question
• In the Column Tools ribbon, check "Sort by Column"
• Remove or change the sort if it's ambiguous
2. Check your data for duplicates
• The column being used to sort may have inconsistent data (e.g. the same category mapped to multiple sort keys)
• Clean the data at source so the relationship is truly one-to-one
3. Use DAX Studio or Tabular Editor to identify the numeric IDs (165694, 605917, 236820) and map them to real table/column names