Forum Discussion
Resolver Ihow to manage reporting lifecycle and avoid cross-workspace sourcing
Hello mr_wizard
have you tried deployment pipelines
Deployment Pipelines allow you to manage content across Development, Test, and Production environments systematically. With deployment pipelines:
• Semantic models and reports can be deployed together across stages.
• Thin reports (live-connected to datasets) will automatically connect to the appropriate dataset as they move through pipeline stages, ensuring consistency without cross-workspace sourcing
Super UserIf you use deployment pipeline, you will be able to have a proper promotion management, with tracking, ie who did it, when and even add notes of the additional features have been added to the prod version. And also you will be able to do some comparisons between versions of different environment.
If all above is not needed, you can just work in 1 workspace, create folders for the different "environments". Not a proper solution, but it works.. You will always publish into the same workspace for "dev/prod/test"
Resolver IWe definitely need (and use) deployment pipelines for both the semantic models and the reports (for many of the reasons that you listed). In order to enforce the no-cross-workspace-sourcing rule while also enforcing the rule that every report in every stage point to Production, I think it's unavoidable to have 6 workspaces and 2 deployment pipelines: 3 workspaces and 1 pipeline for the semantic model lifecycle, and another 3 workspaces and 1 pipeline for the report lifecycle (where the "semantic model" pipeline deploys to the 3 "report" workspaces after it deploys into the Production "semantic model" workspace).
- Tutu_in_YYC
The challenge i see here is: how are you going deploy the semantic model from deployment pipeline for Semantic model into deployment pipeline for Report?
Is this what you are thinking?- mr_wizard
For the semantic model deployment pipeline, I would assign 6 workspaces, where the last 3 are for the report lifecycle. So, the semantic model deployment pipeline would look something like:
Dev Model -> Test Model -> Prod Model -> Dev Report -> Test Report -> Prod Report
I don't think deployment pipelines support parallel deployment. Otherwise, after deployment into workspace Prod Model, I would run parallel deployments into workspaces Dev Report, Test Report, and Prod Report, since the path after Prod Model doesn't need to be linear.
The deployment pipeline for reports would simply be:
Dev Report -> Test Report -> Prod Report
This way, I can uncouple the model lifecycle from the report lifecycle (much like how I uncouple the warehouse lifecycle from the model lifecycle).
- Tutu_in_YYC
I see. Good luck, let us know if you encounter challenges.