Forum Discussion
Question about shared datasets
- 1 year ago
Hey jgeorge ,
Your understanding is correct: when you use the Power BI REST API's /imports endpoint with nameConflict=Overwrite, it only updates the dataset and report that were originally associated with that import, not any other reports that may now be bound to that dataset.
Why test456 Is Not Updated
Although test456 is bound to the test123 dataset, it remains a separate report object. When you import test123.pbix using: POST /groups/{groupId}/imports?datasetDisplayName=test123.pbix&nameConflict=Overwrite
this only updates:
The dataset named test123
The report that was originally imported from test123.pbix (likely also named test123)
Any other reports (like test456) that you have manually rebound to test123 will not be affected by this import. Power BI does not track which reports are re-bound to a dataset after the fact for the purpose of updating on import.
How to Update test456
To update the visual layout or structure of test456, you have two options:
Option 1: Rebind test456 to a fresh dataset
If you want test456 to reflect changes made in the .pbix file (like visuals, report pages):
Re-import the .pbix file again with a different datasetDisplayName.
Then rebind test456 to the new dataset using:
POST /groups/{groupId}/reports/{reportId}/Rebind { "datasetId": "new-dataset-id" }
Option 2: Delete and Re-import the Report
If test456 is just a copy of test123, consider:
Deleting the existing test456 report.
Reimport the .pbix with nameConflict=Overwrite to update both report and dataset.
If needed, rename the report to test456.
For Detailed Information:
Power BI Service - Dataset Concepts
Rebinding Power BI Reports with REST APIs (Community)
Understanding Shared Datasets in Power BI
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam
Hey jgeorge ,
Your understanding is correct: when you use the Power BI REST API's /imports endpoint with nameConflict=Overwrite, it only updates the dataset and report that were originally associated with that import, not any other reports that may now be bound to that dataset.
Why test456 Is Not Updated
Although test456 is bound to the test123 dataset, it remains a separate report object. When you import test123.pbix using: POST /groups/{groupId}/imports?datasetDisplayName=test123.pbix&nameConflict=Overwrite
this only updates:
The dataset named test123
The report that was originally imported from test123.pbix (likely also named test123)
Any other reports (like test456) that you have manually rebound to test123 will not be affected by this import. Power BI does not track which reports are re-bound to a dataset after the fact for the purpose of updating on import.
How to Update test456
To update the visual layout or structure of test456, you have two options:
Option 1: Rebind test456 to a fresh dataset
If you want test456 to reflect changes made in the .pbix file (like visuals, report pages):
Re-import the .pbix file again with a different datasetDisplayName.
Then rebind test456 to the new dataset using:
POST /groups/{groupId}/reports/{reportId}/Rebind { "datasetId": "new-dataset-id" }
Option 2: Delete and Re-import the Report
If test456 is just a copy of test123, consider:
Deleting the existing test456 report.
Reimport the .pbix with nameConflict=Overwrite to update both report and dataset.
If needed, rename the report to test456.
For Detailed Information:
Power BI Service - Dataset Concepts
Rebinding Power BI Reports with REST APIs (Community)
Understanding Shared Datasets in Power BI
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam