Workspace disappearing from Publish list in report when using 'Power BI dataset' as source

[GilesFS]

I have 4 shared workspaces which I have published numerous reports to (from Desktop), however one of them now disappears from the Publish list when my report uses data from an existing/other workspace dataset.

This is inconsistent behaviour as only one particular workspace disappears, not the rest.

Specifics

- I have created various new reports to test this

 - the datasets used are in a different workspace to the one I want to publish to

 - I have successfully published reports using the dataset in question to other shared workspaces

 - if my report uses different data sources, the workspace appears in the list to publish to

[dax]

Hi GilesFS,

I can't reproduce this problem in my environment. It seems that this problem only exist in a particular workspace, right? Did you ser any other setting in workspace? If you re-create dataset in worksapce and use this in powerbi  desktop, will this wok or not? What is type of this workspace?

Best Regards,
Zoe Zhi

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

[GilesFS]

It's a standard workspace, no different from my other workspaces in terms of configuration

It seems that it's intermittently getting confused with "My Workspace" as sometimes when I look at the Workspace list on "https://app.powerbi.com/home", the correct workspace icon is appearing in the list where it should be, but it's name is no longer "PMO" (the actual name) but it's showing as "My Workspace" instead! This would make sense re: when I try to publish it doesn't show the "PMO" workspace because the server is calling it "My Workspace", so I don't see "PMO" and the "My Workspace that I see only publishes it to the real "My Workspace".

I can only think that this is a bug. My workaround in the end is to create a new workspace and copy all the reports over to that one instead. (And if it happens again, then I guess I'll just have to do the same workaround agin - fingers crossed it won't!)