Forum Discussion
Deployment Pipelines Thin reports
- 1 year ago
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 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?