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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
s--turn
Helper II
Helper II

Field name discrepancy causing refresh error

Hello,

I have created a dataflow, and used it to build a report in Desktop.  I then published that report to Power BI online, which created a semantic model as well as the report itself.  I configured a daily refresh on the semantic model.  However, the refresh keeps failing, and the stated reason is that "the 'statuscode_display' column does not exist in the rowset":

sturn_0-1712666348533.png

I thought this would be easy to correct, but weirdly, there is no such field in the blc_eventdelegate table named in the error message.  In the dataflow, the only similarly-named field is called blc_delegatestatus_display.  That's what it's called in the report, too (I have checked in Desktop).  Yet, in the semantic model online, it's there as statuscode_display (see yellow highlight in bottom left):

sturn_2-1712666578403.png

I even deleted the report and semantic model from Power BI online, and republished the Desktop report, but the same error is happening!  Does anyone have any idea where the semantic model is getting this from?

This is the dataflow:

sturn_3-1712666729198.png

 

Thanks in advance for any hints!

 

 

1 ACCEPTED SOLUTION

Hi @GilbertQ , I did (screenshot was in my original post), but what fixed this in the end was going back into Desktop, re-selecting the data flow in the Power Query steps, and then just refreshing the report in Desktop.  I think at some point I changed the columns in the dataflow, but the report hadn't caught up with that change.

View solution in original post

2 REPLIES 2
GilbertQ
Super User
Super User

Hi @s--turn 

 

Could you have a look in your data flow to make sure that that column does not exist?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Hi @GilbertQ , I did (screenshot was in my original post), but what fixed this in the end was going back into Desktop, re-selecting the data flow in the Power Query steps, and then just refreshing the report in Desktop.  I think at some point I changed the columns in the dataflow, but the report hadn't caught up with that change.

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors