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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
tomwwagstaffRIT
Frequent Visitor

SQL connector - coping with schema changes

Hi Power BI community,

 

I published a dashboard to the Power BI service, which includes a "SELECT * FROM" query of a SQL table. The table schema has been altered, and now the dataset fails to update in the Power BI Service, with the error:

 

The 'x' column does not exist in the rowset.

Refreshing the dataset in Power BI desktop succeeds - and appears to refresh the schema, with no complaint about missing / unexpected columns. However, even after deleting the original report and republishing from Power BI Desktop, the data still refuses to update.

 

Any idea how to make the SQL connector robust to schema changes? (other than specifying the columns, which I know is best practice but I want to retain some flexibility for redeveloping the dashboard...)

 

Cheers,

Tom

1 ACCEPTED SOLUTION

Thanks for your suggestions Amy @v-xicai ,

 

The solution turned out to be not just refreshing the query in Power Query Editor, but following that also to refresh the table in the fields pane of the report screen.

View solution in original post

3 REPLIES 3
v-xicai
Community Support
Community Support

Hi @tomwwagstaffRIT ,

 

You can download the pbix file from the report page in Power BI Service, then open in Power BI Desktop to check which visual is broken in Visual pane or which column is created with incorrected syntax in Fields pane . Then you can determine if add to the visuals or not.

 

4.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

There are similar cases you can refer to :Case1, Case2.

 

You may also resolve the issue via the troubleshooting link :https://docs.microsoft.com/en-us/power-bi/refresh-troubleshooting-refresh-scenarios.

 

Best Regards,

Amy

 

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

Thanks for your suggestions Amy @v-xicai ,

 

The solution turned out to be not just refreshing the query in Power Query Editor, but following that also to refresh the table in the fields pane of the report screen.

Hi  @tomwwagstaffRIT ,

 

Does that make sense? If so, kindly mark the right reply as a solution to help others having the similar issue and close the case. If not, let me know and I'll try to help you further.

 

Best regards

Amy

 

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

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

Top Solution Authors
Top Kudoed Authors