Forum Discussion
Rebind - Power BI Rest API clarification
As of 5/14/2020 this is still an issue. I opened a ticket and after some back and forth got this conclusion:
As we discussed over the Microsoft Teams, we also tried reproducing the issue from our end and we are also getting the same behavior which you are getting after downloading .pbix of the reminded dataset. We had escalated this issue to our PG Team and we got the infomation that this is a known bug.
Our PG team is aware of this behavior, and actually this limitation exists in rebind API since it was first published. They will work reagrding the issue and it will take some time to get it fix in future. Below are the steps we followed to reproduced the issue-
dataset 1 (analysis import test) and dataset2 (analysis import test 1) should be similar source and identical
Step1: create connection to dataset 1 and publish as report 1: done- connected to analysis import test
step 2: rebind the report1 to dataset 2: done - now its rebinded to dataset2 (analysis import test 1)
Step 3 : download the report1, the connection still shows to dataset 1(analysis import test) Which is not true in Power BI Service.
The dataset id changed but when we download it still points to dataset 1 (analysis import test)
We are facing the exact same issue with Rebind so thank you for the blog post and link to this forum Anonymous !
For my clarity, after using Rebind API, does the report in the Power BI Service actually point to the correct dataset? And then only when downloading a copy of the report, revert back to the original/incorrect dataset?
Hello Anonymous ,
Yes you are correct. I have observed this behavior while working on such a scenario where the report in the Power BI Service actually points to the correct dataset and then only when downloading a copy of the report, it reverts back to the original/incorrect dataset.