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
starsoul
Regular Visitor

Data source error: The 'xxx' column does not exist in the rowset.

Getting below error message without the name of the table. I have around 100 table in the model and most of them have a description field as a column. Now don't know how to find which table is causing this issue. Refresh all data works fine in Power BI Desktop app. Last time when I encountered this problem, I started deleting tables 1 by 1 and I figured out which table is causing service to fail. Then I refreshed that table manually and published it again and it got fixed. But now again am getting this issue for some other column. I can't delete tables every to find which table this error is referring to, its very time consuming. It should share the Table name which this column doesn't exist. Database used here is MYSQL. As I have mentioned earlier not sure why BI Desktop doesn't through this error only service starts getting failed for refresh.

 

Data source error: The 'DESCRIPTION' column does not exist in the rowset.

Cluster URI: WABI-INDIA-WEST-redirect.analysis.windows.net

Activity ID: xxxxxxx

Request ID: xxxxxxx

Time: 2021-08-21 11:07:35Z

 

starsoul_0-1629546894002.png

 

5 REPLIES 5
v-xulin-mstf
Community Support
Community Support

Hi @starsoul

 

Currently there is no support for retrieving to which specific table there is a problem.

For your current problem, please refer to this post and check if you have a similar operation.
As a workaround, you can narrow it down to a table with similar actions.

If you still have some question, please don't hesitate to let me known.‌‌

 

Best Regards,

Link

 

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!

@v-xulin-mstf Thanks for responding. Without table name information its anyway difficult to find the problematic table when you are dealing with 100+ tables in a model. So in some logs it should provide the table information where service found the issue, which it does in other scenarios. From Microsoft support they shared list of few tables which helped. 

Hi @starsoul

 

Okay, looking forward your good news!

It would be great if you could share the solution with us!

😉

Best Regards,

Link

 

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!

Greg_Deckler
Super User
Super User

@starsoul You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".


@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
The Definitive Guide to Power Query (M)

DAX is easy, CALCULATE makes DAX hard...

@Greg_Deckler This issue is not listed. I have created another post for the same and also raised a support ticket with Microsoft. Thank you for responding. 

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