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 UserHello 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 IYes. However, I don't understand how deployment pipelines resolve the problem. Both the semantic models and the reports need to follow a lifecycle (Development, Test, Production). As a thin report moves through each stage (workspace) of the lifecycle, to not encounter cross-workspace sourcing, its semantic model needs to be "local" (i.e., in the same workspace as the report). But, because of our rule that we always point downstream layers to the Production "environment" of previous layers, that forces the semantic model in each stage (workspace) of the report layer to be the Production version. Whether we deploy manually or in a pseudo-automated way (with deployment pipelines), I don't see any way to avoid cross-workspace sourcing, unless we do something like deploy the Production version of each semantic model four times (first to the Production workspace of the semantic model, then again to the Development workspace of the report, then again to the Test workspace of the report, and lastly to the Production workspace of the report). What am I missing?