Forum Discussion
Issue Publishing to PowerBI Service
Despite the good suggestions here, in the end there was no alternative to just re-publishing with a new name and re-sharing. This time, however, I have shared as an app from within the workspace which should prevent the sharing complications if it breaks in the future.
Hey Anonymous5 ,
The error message you're encountering “Couldn’t publish to Power BI: A semantic model or report named [xyz] already exists and is set up with cloud refresh” is typically caused when:
The report you're trying to re-publish has the same name and dataset as the one already deployed in the Power BI Service.
The existing dataset in the workspace is cloud-refreshed and linked to an underlying source, which prevents overwriting via re-publish from Desktop.
Why Your Workarounds Didn’t Work
Turning off cloud refresh only disables the schedule, not the dataset’s cloud configuration. It remains linked to the workspace metadata.
Downloading and re-uploading also preserves this link unless you: Remove the dataset or Publish it under a new name.
Other reports working implies the issue is isolated to this one report’s dataset linkage/config.
Fix Without Breaking Existing Links
Option 1: Use the “Replace” option in Power BI Service
Go to Power BI Service.
In the workspace, locate the dataset/report.
Select “Download the PBIX” (you already did this).
In Desktop, make your changes.
Save it with a new name like Report_v2.pbix.
In Power BI Service, go to Workspace > Settings > Datasets.
Manually delete the old dataset only if you're certain you won’t break downstream artifacts.
Publish the new .pbix.
This still breaks shared links unless you reassign permissions and reconfigure dashboards.
Option 2: Use Deployment Pipelines (Recommended for Shared Workspaces)
Use Deployment Pipelines to move content between Dev → Test → Prod.
Upload the revised report to the Dev stage.
Deploy it forward, letting Power BI handle dataset refresh links.
Option 3: Edit via Power BI Service
If your changes are minor:
Instead of using Desktop, open the report in Power BI Service > Edit Report.
Make the changes directly in the browser.
Save—this avoids breaking the refresh config.
This only works if your report doesn't use unsupported visuals or DAX features.
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam
Hello Nasif_Azam
Thank you for the thorough and thoughtful reply. I am interested in your deployment pipeline solution and I will take this up with our workspace team. Also, the change I need to make involves tweaking the underlying query so it needs to be done in PBI desktop.
one additional question, if I am able to publish the new dataset without breaking the links, will the existing publish process be broken going forward with this report (at least using the standard method)? The report issues Snowflake and SharePoint data connections. It would be ideal if this report functioned like the several others that allow simple publishing from PowerBI Desktop when changes or updates are neeed.
Thanks for the follow-up! Since you’re updating the underlying query and want to preserve existing links and scheduled refresh capability, it’s essential to understand what happens when you overwrite or recreate a dataset/report in Power BI.
Yes the publishing process will work normally going forward but with conditions. If you’re able to overwrite the existing dataset without changing its structure (e.g., table names, column names, relationships), the report can continue functioning as before.
You can publish normally in the future if:
- You successfully publish from Desktop and overwrite the existing report and dataset (meaning the GUID stays the same).
- The data source credentials and refresh configuration are still valid after publishing.
- You don’t rename or remove key tables/columns used in visuals, filters, or measures.
Once this overwrite is done cleanly, subsequent updates via Power BI Desktop will behave normally again.
Your publishing will break if:
- You delete and re-create the dataset with a new GUID (this breaks links, dashboards, refresh settings, and permissions).
- You publish with a different dataset name, even if the report name is the same.
- You introduce breaking changes to the schema (e.g., deleting columns used in visuals).
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam