Deployment report from one workspace to another

[SebastianM]

Hello,

I'm looking for a solution of reports deployment connected to semantic models.

Case (simplified):

In DEV stage I have 2 workspaces

• Workspace A: where Semantic Model is
• Workspace B: where report is published. This report is live connected to Semantic Model from Workspace A.

And everything works ok.

Now I want to push to TEST stage.

• I'm just publishing semantic model from DEV.workspace_A to TEST.workspace_A - this is fine (I can easily swap url to database or some other connection link I'm using using Parameters in semantic model)
• With report itself I don't know how to properly publish it to TEST.workspace_B so it will point to semantic model from TEST.workspace_A

I know that I can open report, manually swap connection to other semantic model but this is not the solution in case of tens of reports...

Any ideas how to solve it?

[marcosvin · Accepted solution]

Hello!

If you have premium capacity in your organization, you can use the "Deployment pipelines" feature, which allows you to automate the movement of objects between DEV, Test, and Production workspaces.

Reference: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/intro-to-deployment-pipelines

[SebastianM]

Hi @marcosvin ,

I was pretty sure that deployment pipelines will not solve my issue - that this feature works only for a case workspace-to-workspace.

After checking again doc and after some tests it work like a charm 🙂

Doc says (https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process)

Deployment pipelines automatically binds items that are connected across pipelines, if they're in the same pipeline stage. When you deploy such items, deployment pipelines attempts to establish a new connection between the deployed item and the item it's connected to in the other pipeline. For example, if you have a report in the test stage of pipeline A that's connected to a semantic model in the test stage of pipeline B, deployment pipelines recognizes this connection.

Thanks!!