Forum Discussion
Cannot Select a Destination Workspace when Publishing - After Upgrading to the New Workspace
Hello! Last night I upgraded a workspace (call it A). I clicked on "Upgrade Now", with docs listed here:
https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-upgrade-workspaces
Then this morning, I went to publish a report that was already published in A and connected to a dataset in A, to a new workspace.
Well, Desktop doesn't prompt me to select a workspace! When I click "Publish", it auto-publishes to A. Other reports in A, which were connected to a dataset in B (which was always a modern workspace), can be republished to other workspaces as expected.
I'm not sure what else could be the problem. This is entirely new behavior, and it seems to be connected to my upgrade of the workspace. I'd appreciate any input!
Thanks,
Amon
Well, I ended up publishing my dataset to an "established" (always new version) workspace so I could get my reports published and available by my deadline. Believe me, I quit and restarted Power BI each time I opened a report.
I've since rebooted and changed my reports to connect back to the original dataset, in A (above). Now Publishing works. So either (1) rebooting or (2) connecting to another (identical) dataset in a "normal" workspace, then switching back to the original dataset worked. Or maybe both together. I'll never know because I have no other reports in that folder created prior to the upgrade, connected to datasets in that folder created prior to the upgrade. I consider this resolved.
2 Replies
- aseagullHelper IV
Well, I ended up publishing my dataset to an "established" (always new version) workspace so I could get my reports published and available by my deadline. Believe me, I quit and restarted Power BI each time I opened a report.
I've since rebooted and changed my reports to connect back to the original dataset, in A (above). Now Publishing works. So either (1) rebooting or (2) connecting to another (identical) dataset in a "normal" workspace, then switching back to the original dataset worked. Or maybe both together. I'll never know because I have no other reports in that folder created prior to the upgrade, connected to datasets in that folder created prior to the upgrade. I consider this resolved.