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

will not update data

Hi, Guys!

I have the issue with dataset refresh in power Bi service.
Situatio is next: I using gateway to connect my pc to connect mysql database and we deleted or rename one of the column in in rone of the tables id DB. And then refresh in Power Bi service dosent work error saying that missing column "X". But in power Bi desktop I can refreshed report publish again and its workes perfectly then. So maybe there is some way to make dataset refreshed directy in power Bi service then column in DB changed, except going to power Bi desktop.

1 ACCEPTED SOLUTION
v-xiaoyan-msft
Community Support
Community Support

Hi @AndrejZevzikov ,

 

Whenever you refresh your data, Power BI must query the underlying data source. The entire refresh process consists of multiple stages, depending on the storage model of your dataset.

 

Power BI does not import data through a connection that operates in DirectQuery/LiveConnect mode. Instead, whenever a report or dashboard queries a data set, the data set returns results from the underlying data source. power BI transforms the query and forwards it to the data source.

 

Power BI imports the data from the original data sources into the dataset. Power BI report and dashboard queries submitted to the dataset return results from the imported tables and columns. You might consider such a dataset a point-in-time copy. Because Power BI copies the data, you must refresh the dataset to fetch changes from the underlying data sources.

 

So when you delete or rename a column in the id DB of one of the tables. You need to reconnect to the desktop and republish, this is by design.

 

For more information, please see:Data refresh in Power BI 

 

Hope it helps,


Community Support Team _ Caitlyn Yan


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

View solution in original post

6 REPLIES 6
v-xiaoyan-msft
Community Support
Community Support

Hi @AndrejZevzikov ,

 

Whenever you refresh your data, Power BI must query the underlying data source. The entire refresh process consists of multiple stages, depending on the storage model of your dataset.

 

Power BI does not import data through a connection that operates in DirectQuery/LiveConnect mode. Instead, whenever a report or dashboard queries a data set, the data set returns results from the underlying data source. power BI transforms the query and forwards it to the data source.

 

Power BI imports the data from the original data sources into the dataset. Power BI report and dashboard queries submitted to the dataset return results from the imported tables and columns. You might consider such a dataset a point-in-time copy. Because Power BI copies the data, you must refresh the dataset to fetch changes from the underlying data sources.

 

So when you delete or rename a column in the id DB of one of the tables. You need to reconnect to the desktop and republish, this is by design.

 

For more information, please see:Data refresh in Power BI 

 

Hope it helps,


Community Support Team _ Caitlyn Yan


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

Correct me if I wrong, 
if i created my report (in power Bi desktop) with DirectQuery option I will fix my issue, but i know (i could be wrong) if report cretaed with DirectQuery options and have some complex calculations it can have some issues with calculations results.

Hi @AndrejZevzikov ,

 

Sorry I may not have explained it clearly. Switching storage modes does not solve this issue. The suggestion above means that no matter what storage mode you use, the refresh will go to the data source to find a matchable item based on the metadata (such as column name, etc.) used by PBIX , and when this item is deleted, it cannot be found, so an error will be reported, in which case the intelligent choice is to republish or restore the deleted column.


Also, you are right, there are indeed some limitations when using direct query, for details please check:

Limitations of using Direct Query 

 

Hope it helps,


Community Support Team _ Caitlyn Yan


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

tctrout
Resolver III
Resolver III

I am very interested if anyone can explain this.

I have experienced the same issue, with a work around, but still do not know why this occurs or how to fix it without a work around.

 

What we had tried without success:
1. Deleted the dataset and report. Re published

2. Deleted the  datasource connection cache within the PBIX

3. Restarted the capacity

 

What worked for us:

1.  We added the deleted column back in source. 

I finally figured out a work around for this as opposed to adding the deleted column back to the source.

In the Power Query Editor, go to the Navigation step of the impacted table.  Choose any other table other than the one that is impacted & click OK.  Go back to the Navigation and pick the table that you actually need and was impacted. 

This appears to reset the previous cache it was hung up on.

It's look like very unefficent solution ( I hope there is other way to solve this.

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 Kudoed Authors