Forum Discussion
Problems with Deployment Pipelines and Models in Different Workspaces
Greetings, all. Ran into an issue and was curious if anyone else has seen this/have a fix.
We have a model in Workspace A and a report in Workspace B that references the model. We are trying to deploy the report to Workspace C via a Deployment Pipeline but are getting an error about related datasets needing to be included (see image below). This is a live-connected report, so there's NEVER going to be a case where the model lives in the workspace with the report unless we literally store the report in that workspace, which we're avoiding for process/security reasons.
How can we deploy reports that are live-connected?
Hi arpost
To be totally honest, what I have done in the past when reports are live connected is simply upload those reports to the relevant workspaces. Because they are live connected they should only be visuals that are changing and report pages changing. Between the deployments as all the other work should be done in the semantic model which is being live connected to.
I suspect the problem you are facing is due to Auto-Binding. I'm guessing Workspace B & C are part of a deployment pipeline. Workspace A needs another workspace with its own pipeline (if you don't have it already).
Power BI is designed that your modelling workspaces and your reporting workspaces need to have the same Dev/Test/Prod styles.
Its expected that your DEV model and your Test model may have different data. You also likely might have modelling changes that will break test, so you need to separate out those distinct publishing steps to ensure your Dev/Test/Prod versions are all aligned with the Dev/Test/Prod reporting.
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
4 Replies
Hi arpost
To be totally honest, what I have done in the past when reports are live connected is simply upload those reports to the relevant workspaces. Because they are live connected they should only be visuals that are changing and report pages changing. Between the deployments as all the other work should be done in the semantic model which is being live connected to.
I suspect the problem you are facing is due to Auto-Binding. I'm guessing Workspace B & C are part of a deployment pipeline. Workspace A needs another workspace with its own pipeline (if you don't have it already).
Power BI is designed that your modelling workspaces and your reporting workspaces need to have the same Dev/Test/Prod styles.
Its expected that your DEV model and your Test model may have different data. You also likely might have modelling changes that will break test, so you need to separate out those distinct publishing steps to ensure your Dev/Test/Prod versions are all aligned with the Dev/Test/Prod reporting.
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Hi arpost,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to Anonymous & GilbertQ for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Hello arpost,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
