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
Resolver IFor 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).
Super UserI see. Good luck, let us know if you encounter challenges.