Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
jgeorge
New Member

Question about shared datasets

Hi, I have a question about Power BI REST APIs for shared datasets. Say I have a report named test123, and I have a dataset named test123 (created from the same .pbix file when I imported). Now, I have another report test456. It was originally bound to dataset test456 (which was created from the same .pbix when I imported test456 report), but then I rebound to use test123, and then deleted the test456 dataset. If I use /imports?datasetDisplayName=test123.pbix&nameConflict=Overwrite, this will update both test123 dataset and test123 report. But how can I update the test456 report? It no longer is associated with the test456 dataset, but when I update the test123 dataset using /import, it only updates the test123 report, not the test456 report.

1 ACCEPTED SOLUTION
Nasif_Azam
Super User
Super User

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):

  1. Re-import the .pbix file again with a different datasetDisplayName.

  2. 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:

  1. Deleting the existing test456 report.

  2. Reimport the .pbix with nameConflict=Overwrite to update both report and dataset.

  3. If needed, rename the report to test456.

 

For Detailed Information:

Rebind Report to Dataset

Clone Report

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

View solution in original post

5 REPLIES 5
v-mdharahman
Community Support
Community Support

Hi @jgeorge,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are facing issues in updating a your second report as its dataset is changed to the first one but even after that report is not updating. As @Nasif_Azam has already responded to your query, kindly go through his response and check if your issue can be resolved.

 

I would also take a moment to thank @Nasif_Azam, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

 

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

Hi @jgeorge,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If so, it would be really helpful for the community if you could mark the answer that helped you the most. If you're still looking for guidance, feel free to give us an update, we’re here for you.

 

Best Regards,

Hammad.

Hi @jgeorge,
I just wanted to follow up on your thread. If the issue is resolved, it would be great if you could mark the solution so other community members facing similar issues can benefit too.
If not, don’t hesitate to reach out, we’re happy to keep working with you on this. 

 

Best Regards,

Hammad.

Hi @jgeorge,
We noticed there hasn’t been any recent activity on this thread. If your issue is resolved, marking the correct reply as a solution would be a big help to other community members.
If you still need support, just reply here and we’ll pick it up from where we left off.

 

Best Regards,

Hammad.

Nasif_Azam
Super User
Super User

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):

  1. Re-import the .pbix file again with a different datasetDisplayName.

  2. 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:

  1. Deleting the existing test456 report.

  2. Reimport the .pbix with nameConflict=Overwrite to update both report and dataset.

  3. If needed, rename the report to test456.

 

For Detailed Information:

Rebind Report to Dataset

Clone Report

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

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.