Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
PeterJMayes
Frequent Visitor

Refresh failed

For a few weeks both published report and in desktop were refreshing correctly (scheduled in web). Two days ago I started to get failed refresh on the three reports that I had created based on the same data set.

 

Error being returned in all three reports:

Column '_mcs_commonlocationid_value' in Table 'incidents' contains blank values and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.

 

I've checked this column in the Data view and there are no blank records. I checked the relationships in the Model view and this column is not in a relationship with any other table in the model.

 

Any thoughts would be welcomed.

1 ACCEPTED SOLUTION
ibarrau
Super User
Super User

Hi. That usually an error when you have one blank in a column that is used in a relationship. Try refreshing Power Bi Desktop to see if the error is there. Even if you can't find the blank for that column used in relationship, add a stop in power query editor to "Remove blank rows" for that column. That might solve it.

Hope it helps,


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

Happy to help!

LaDataWeb Blog

View solution in original post

2 REPLIES 2
ibarrau
Super User
Super User

Hi. That usually an error when you have one blank in a column that is used in a relationship. Try refreshing Power Bi Desktop to see if the error is there. Even if you can't find the blank for that column used in relationship, add a stop in power query editor to "Remove blank rows" for that column. That might solve it.

Hope it helps,


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

Happy to help!

LaDataWeb Blog

Hi

Many thanks for the thoughts. Both the online and the desktop refreshes failed. However your response got me to investigate in Query Editor a bit further. Turns out the offending field is not needed in the data model for the report so I removed it. The reports now work without any omissions.

PJ

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors