Problems with Deployment Pipelines and Models in Different Workspaces

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