Decommission a Dataset After Clearing Dependents
A 4-step recipe with Power BI. We can help you get access.
Recipe · 4 steps
Decommission a Dataset After Clearing Dependents
with Power BI · Analytics & BI Management
Retire a dataset after removing the report that depends on it.
- Read the dataset to confirm it exists and to record who configured it, so the retirement is logged against a real, identified model.
- List every report visible to the caller. Each report carries the datasetId it is bound to, so this collection is what identifies the dependents that must be cleared before the dataset can be safely removed.
- Delete the nominated dependent report so no report is left pointing at a dataset that is about to disappear. Returns 200 with no body.
- Delete the dataset now that its dependent report has been removed. This is irreversible. Returns 200 with no body.
What you'll need to have ready
- datasetId: The identifier of the dataset to decommission.
- dependentReportId: The identifier of the report bound to this dataset that should be deleted before the dataset is removed.
For your developer
Arazzo workflow power-bi:dataset-decommission, 4 operations: getDataset → getReports → deleteReport → deleteDataset. Specs on APIs.io.