Forum Discussion
Helper VHow to reconnect Semantic Model in different Workspace?
Hi all,
I'm working and building report in Power BI Desktop with Live Connection to Power BI Dataset (Semantic Model) in one of my client Workspace (lets say A). It's been Published in the different Workspace B (report and semantic model), but I'm not aware that in my PowerBI desktop is actually still connected to the one in Workspace A.
Now the semantic model in Workspace A is removed, and I experiencing "cannot connect to datasource" if I open my report from Power BI Desktop.
In Workspace B, where I still can find my published report (as well as the copy of semantic model), initially have the error sign and the settings display no data source, but I'm able to connect to the semantic model in Workspace B and able to open the report in Fabric.
But if I download this report, with option available only "a copy with Live connection", which is what I wanted and expected.
But when open this downloaded report in Power BI desktop, it will stay as cannot connect.
Edit will said not set to an object. And if hit Transform data, it will keep loading saying "workin on it" with after several "meaningful" time spend (and loss), end up failed to connect.
Anyone know how to change datasource safely which is same semantic model only it is on different Workspace ?
Thanks,
Hi VoltesDev ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you suparnababu8 for the prompt response.
Saving as PBIP only works before the original dataset is deleted. Once Workspace A’s model was removed, the link is broken - so opening the PBIX just shows a blank/untitled report. Connecting again to Workspace B’s model creates a new report, which is why visuals don’t come back.
Even though in Service you reconnected to the model in Workspace B, the PBIX download still keeps the old Workspace A reference. That’s why Desktop says “cannot connect.”
The safe fix is to use the Power BI REST API “Rebind Report” (or PBIP Developer Mode going forward). Rebinding updates the report to point to Workspace B’s dataset, so visuals are retained and future downloads will open correctly.
7 Replies
- suparnababu8
Super User
Hi VoltesDev
You could try with below sugegstions
- You can use PBIP format. save your desktop file as .pbip file and edit the workspace B connection in pbip file then open it in desktop. Please go through this articel How to switch report live connection using Power BI Developer Mode — DATA TRAVELING - Guilherme Joaquim's Blog it may helps you
- Second one is, PBI REST API method to chnage the semantcimodel data source. it helps you to reetain all what you developed in that report. Please go thorugh this aricle Rebind (Switch) Reports to different Power BI Semantic Model – Hari BI Academy It may helps you
Please let me know if it helps you,
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
VoltesDevHi,
Is the "save as PBIP" before the report cannot connect and open?
Since now, after "unable to connect": and press cancel, it will just "Untitled report", with blank just like a new report.
I can connect again (Get data) with the new workspace B with "actually" same Semantic Model, but all my visual in that report are gone. It is just like a new report connect to a new Semantic Model. Although it is initially open the report "that failed to connect"
Thanks,
Thanks,
- VoltesDev
What I don't understand as well is why after the report in the new Workspace B, which already "reconnected" to the semantic model in the same Workspace B, after downloaded, I'm still cannot open it from my Power BI Desktop.
Thanks,
v-venuppuCommunity Support
Hi VoltesDev ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you suparnababu8 for the prompt response.
Saving as PBIP only works before the original dataset is deleted. Once Workspace A’s model was removed, the link is broken - so opening the PBIX just shows a blank/untitled report. Connecting again to Workspace B’s model creates a new report, which is why visuals don’t come back.
Even though in Service you reconnected to the model in Workspace B, the PBIX download still keeps the old Workspace A reference. That’s why Desktop says “cannot connect.”
The safe fix is to use the Power BI REST API “Rebind Report” (or PBIP Developer Mode going forward). Rebinding updates the report to point to Workspace B’s dataset, so visuals are retained and future downloads will open correctly.
