Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
hi all,
this morning i have modified one of my datasets with the desktop version and after i saved the modifications i published the dataset to the webversion. Before closing the desktopversion, i got the message: "publishing is complete. However we couldn't refresh your dataset". Did a manually refresh with the desktop version which went well, but if i go to the web, i can run "refresh now" but nothing happens. Tried a different dataset and the strange thing is that i managed to update this dataset but others didn t update as well (it does not give any error messages and does not show that you have started a refresh on demand...). Checked the on-prem gateway with the most recent version and they both seems to be the same (both have version 14.16.6584.1)....
Any ideas what to do???
thanks in advance
M
Solved! Go to Solution.
Hi there,
I have the same issue, I managed to get a workaround but it's not perfect.
So I store .pbix file on a SharePoint for a Version Control.
I went to Power BI Service -> Get data -> Files (Get) -> Pointed to my SharePoint location and it successfully published the report. But now I have two reports with same name... so it's not ideal.
I'm also wondering how this issue could be fixed.
I was able to solve this by creating a new blank PBIX file of the same name and uploading it. Then open up the original pbix and reupload. This approach retains all of the lineage reports.
what you also could do is to open the pbix in desktop, go to the datasourcesettings and delete the one that is giving issues. After deleting create a new one and the dataset will still be working. Publish the Pbix and all reports are still okay.... In my case it worked.
Hi
I have faced the same issue a couple of times. Would like to have a solution for this. I always delete the dataset from the Power BI workspace and then re publish it. It works for me.
Cheers, Alba
Hi Alba,
I am trying to delete my dataset from service but not be able to delete so in that case what should we do??
TIA
Hi there,
I have the same issue, I managed to get a workaround but it's not perfect.
So I store .pbix file on a SharePoint for a Version Control.
I went to Power BI Service -> Get data -> Files (Get) -> Pointed to my SharePoint location and it successfully published the report. But now I have two reports with same name... so it's not ideal.
I'm also wondering how this issue could be fixed.
Hi all!
I’m experiencing the same problem! I have an API table powered by Python. I connected to this table through Get Data → Semantic Models in Power BI in Live Connection and created a report. Initially it worked well but after few days, when I publish the report from Desktop to Service, I receive the following error.
For example, if I have a report on Desktop and I want to overwrite a version present on Service, after publishing, I am unable to view the updated report. However, if I publish it with a different name, I can see the changes, but this doesn't help me.
I’ve cleared the cache, but it didn’t solve the issue. Can someone help me? Thanks.
This solution was not the right solution for me.
When I had this error I had to go into Power BI desktop and clear the Cache items.
This is found under
File -> Options and Settings -> Options -> Data Load
Then Clear the
1. Data Cache Management Options
2. Q&A Cache Options
3. Folded Artifacts Cache Options
only after doing this did my report publish with out this error.
apart from workaround do we have the permanent souliton for this? any update fix issue link?
hi MXD,
thanks for the workaround, if there is no other solution offered i will certainly give your solution a try. Hope there is a solution for this, checked again all datasource connections within the datagateway and they seems to be working properly.... As Power bi is a part of Office365, i hope there were no changes on that level that could affect the way of working in PBI.... Anyway, let's wait if there is a good solution...
thanks!!
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
86 | |
82 | |
70 | |
49 |
User | Count |
---|---|
143 | |
125 | |
108 | |
60 | |
55 |