Forum Discussion
Request: Deployments pipelines should support centralized datasets
Hi Anonymous ,
Reports can be managed in pipelines even is they are connected to external datasets.
whenever you deploy report update across the stages, it will keep pointing to the same shared dataset.
You can also manage 'central datasets' WS in pipelines.
However, managing both datasets and connected reports in separate pipelines is still not working in an optimal way, as there's no built-in way to connect each dataset in each stage with the correlated reports in each stage.
We recommend that for now, you connect all reports in all stages to the Prod dataset. in the 'central datasets' pipeline, keep few reports for testing in each stage, so that any change in datasets will be verified on reports before hitting Prod.
If you still encounter problems in some reports, you can use the dev/ test stages to fix it in each pipeline, and deploy to Prod.
Hope it was clear.
This may be a mixing of two concepts - or me misunderstanding the issue.
concept 1: Ability to use shared datasets across multiple workspaces: allows disparate audiences to be served with the same set of master data, but filtered/restricted according to the audience. Reduces development effort, avoids duplication of data, gets you closer to the "one source of truth" fallacy. Sorry, ideal. I meant to say ideal.
concept 2: Ability to speed up development and testing proess without impacting actual production systems. DEV and ITG workspaces can be pointed to datasets that have a reduced but still representative subset of the data, and can also emulate flush&fill events that may not be desirable in production
Neither concept needs deployment pipelines, but the second concept sure benefits from them.