Forum Discussion
Deployment Pipelines Thin reports
We need to follow best practices with split models and reports, moving them with Deployment Pipelines in Power BI
We have 4 workspaces, dev and test have both Dataset and reports , prod models should contain only models and Prod report only the reports, connected to the prod models workspace.
Dev -> Test -> Prod Models -> Prod Report
Now, deploying from Prod Models to Prod Reports demands that i have both dataset and report in that workspace, not great, but fine. I get it, hard to deploy an object from a workspace that does not exist.
Now i want to deploy only the reports to my Prod Reports workspace, and them still connected to the dataset in my Prod Models workspace
I could sware that this worked in the past, and that i tested it., but now the report cannot exist in a workspace if the dataset is not.
Anybody have a workaround for this? Am i missing something?
Hi Anonymous
Your split model and report deployment using Power BI Deployment Pipelines is following best practices, but reports in Prod Reports workspace lose their dataset binding because Power BI now requires datasets and reports to exist in the same workspace during deployment. The best solution is to manually rebind reports after deployment via Power BI Service by selecting the report and changing its dataset to Prod Models. To automate this, use the Power BI REST API (Rebind Report endpoint), which updates the report’s dataset connection post-deployment. Another approach is to use thin PBIX reports in Power BI Desktop, manually connecting them to the Prod Models dataset before publishing. If maintaining separate workspaces is an issue, consider using Power BI Apps to distribute reports instead. The REST API method is ideal for automation, while manual rebinding is a quick workaround.
4 Replies
Hi Anonymous
This certainly works if you do it manually, where you create a semantic model and then create a 3rd report connected to the semantic model. And the thin report is uploaded to an alternative workspace. I'm not sure if something has maybe changed with the deployment pipelines?
Hi Anonymous
Your split model and report deployment using Power BI Deployment Pipelines is following best practices, but reports in Prod Reports workspace lose their dataset binding because Power BI now requires datasets and reports to exist in the same workspace during deployment. The best solution is to manually rebind reports after deployment via Power BI Service by selecting the report and changing its dataset to Prod Models. To automate this, use the Power BI REST API (Rebind Report endpoint), which updates the report’s dataset connection post-deployment. Another approach is to use thin PBIX reports in Power BI Desktop, manually connecting them to the Prod Models dataset before publishing. If maintaining separate workspaces is an issue, consider using Power BI Apps to distribute reports instead. The REST API method is ideal for automation, while manual rebinding is a quick workaround.
Hi!
Thank you for the reply!
Yes i am currently doing it manually, the rest api sounds tempting but i feel that the deployment procedure now becomes a hassle using 2 solutions to get it to work.
As i feel certain that this has worked before, do you have any input if this is true, and a change has been made?
Thanks again
Hi!
Yes currently we are doing it manually, but i could sware that this worked with deployment pipelines when i tested it pre quote to customer.
I have no choice but to do it manually, but as i am certain it worked before, i wonders if i was missing something, i read a bit about autobinding, and tested a few solutions but it loks like im stuck with manual for now.
Thank you for the reply
