This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi,
I have this workflow
Did a deep down and found that this exceptions occurs due to
{
"Version": 2,
"Connections": [
{
"Name": "EntityDataSource",
"ConnectionString": "*****"
"ConnectionType": "pbiServiceLive",
"PbiServiceModelId": ******,
"PbiModelVirtualServerName": "******",
"PbiModelDatabaseName": "d*******3"
}
],
"RemoteArtifacts": [
{
"DatasetId": "f*******c",
"ReportId": "1********6"
}
],
"OriginalWorkspaceObjectId": "9**********7"
}
If we change the PbiModelDatabaseName to the target workspace dataset Id would it work?
If so how do we change it dynamically (either REST API or Tabular Editor), also what value would we need to provide?
If above changes is not possible what else could we try to accomplish the same?
Are you using Microsoft Fabric Git integration as part of your CI/CD strategy? If so, it might be a good idea to test working with the Power BI Desktop Project instead:
Power BI Desktop projects (PBIP) - Power BI | Microsoft Learn
Hi Kevin, No we dont have the requirement to work with Power BI Desktop hence we cannot be using PBIP, we needed it to be part of the service
@Ahmed-Elfeel , Thanks for the response,
When you say rebind after publishing the report - we are doing the rebind after publishing the reports to target workspace using CI/CD (is this what you meant or something else ?)
also
Then Download the PBIX (now it connects to the correct dataset) - after the CI/CD rebind still it points to dev Dataset (do you think this will be different if we do it in service?)
Note: We are not using Power BI desktop in the above process all the code are either in CI/CD or we use C# code to perform actions
We also tried an alternative with using blank report
- create a blank report in target workspace(now this points to a correct dataset)
- get the rebound report and paste the layout file from rebound report to blank report
- post the update blank report - This will successed
BUT!!, the problem is we will lose all the themes and images and all other things that was present with rebound reports, do we have any workaround or alternative for this?
Hello @ChetanK004,
At the moment, Power BI does not support updating live connection metadata inside a PBIX like PbiModelDatabaseName through API or tooling. Because of this limitation, scenarios like CI/CD-based republish of live-connected reports are restricted.
If this capability is important for your deployment flow, I would recommend raising this as an Idea on the Microsoft Fabric / Power BI Ideas forum. That way, the product team can review it and other users facing the same issue can vote on it.
Fabric Ideas - Microsoft Fabric Community
Regards,
Community Support Team.
Hi @ChetanK004,
Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.
Thank you for being part of the Microsoft Fabric Community.
HI @v-hjannapu ,
Here is the idea have posted in the forum https://community.fabric.microsoft.com/t5/Fabric-Ideas/Ability-to-Change-the-origin-dataset-connecti...
Hi @ChetanK004,
Thank you for sharing your idea in the Ideas forum.
We appreciate your contribution. Please note that Microsoft regularly reviews ideas shared by the community, and your suggestion may be considered for future updates.
Thank you once again, and we encourage you to continue engaging with the Microsoft Fabric Community.
Best regards,
Community Support Team.
Hi @ChetanK004,
I hope you are doing well today ❤️☺️
So when you Rebind a report in the Power BI Service only the service-side binding is updated. The internal connection metadata stored inside the PBIX file Itself is not changed. Also when you download a live-connected PBIX it will still point to the original Dev dataset which causes PowerBIModelNotFoundException when you modify and republish it to a different workspace.
Note: There is no supported API or tool (REST, Tabular Editor, XMLA) that can modify live connection metadata inside a PBIX file (Live semantic model connections cant be parameterized or dynamically updated)
The only Approach I see is to Rebind after publishing the report:
POST https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/reports/{reportId}/Rebind
{
"datasetId": "target-dataset-id"
}if you want to Edit the PBIX...you can:
Then Download the PBIX (now it connects to the correct dataset)
If you need more details about Rebinding the report:
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |