Issue Publishing to PowerBI Service

Hi Anonymous5 

The error message you're encountering — “A semantic model or report named [name] already exists and is set up with cloud refresh” — suggests that Power BI is blocking the publish action because it detects a conflict between the existing dataset (semantic model) in the shared workspace and the new version you’re attempting to overwrite. Even though you’ve already disabled cloud refresh, Power BI may still retain background configurations (such as scheduled refresh metadata or dataset bindings) that prevent overwriting via publish from Desktop.

What complicates the issue is that:

• You are the report owner.

• Other reports can still be published normally to the workspace.

• Publishing the same file to My Workspace works fine.

• Even downloading the published version from the Service and trying to republish it fails — which confirms it’s not a local or content-based issue.

This suggests there may be a metadata corruption or lock associated with that specific dataset in the Premium workspace, potentially caused by orphaned refresh settings, deployment pipelines, or governance policies applied via Power BI Service or external tools (like Fabric pipelines or deployment rules).

To avoid breaking shared links but still resolve this:

1. Try uploading via Power BI Service — go to the workspace and use the "Upload a file" option instead of publishing from Desktop. This sometimes bypasses the conflict.

2. Check for deployment pipeline linkage — if this report is part of a deployment pipeline, its source model may be locked from direct Desktop overwrites.

3. Inspect the dataset's settings — check for refresh plans, dataflows, parameters, or lineage views that might still be referencing the old version.

4. Use ALM Toolkit to compare your local .pbix model with the version in the service — this can help identify schema or structural mismatches that might be blocking the publish.

5. As a workaround, publish the new version under a temporary name, then in Power BI Service:

   • Delete the original dataset (not the report).

   • Rebind the existing report to the new dataset using "Manage Report > Settings > Dataset".

   • Rename the dataset back to its original name.
     This will preserve your report URL and shared link while updating the underlying model.

If none of these steps work, it may require admin intervention using PowerShell or REST API to clear residual metadata, or you may need to raise a support ticket with Microsoft due to a workspace-level backend lock.