Forum Discussion
How to Change Live Connection on Report Published in Service and Maintain Same Report URL
- 5 years ago
v-xiaotang I had to publish it, take the new URL and we had to reprogram our portal using the new URL. I never did figure out how to get this to work as expected.
collinq Thank you for response. I too expect it to work as you describe; unfortunately, it does not. I did not change the report at all, other than pointing it to the new PBI dataset, and then I republished the report to the same exact workspace as the original, with the same exact report name. Power BI then created a second instance of the same exact named report in the same workspace, which has to be a different URL as it shows up as two distinct reports, but with the same exact name.
Hi Shelley ,
I am wondering if there is a space or something else "invisible" that is different between the two reports. You should not be able to have two reports with the same name in the same workspace. In fact, you should get this error message that you are overwriting something. I created a test PBI file caleld "TestOverwrite". I saved and published it and then I opened it again, made a change and published again to the same spot and received this error message.
If you are sure that the report is exactly the same name then I suggest opening a ticket with Microsoft and let them help sort it out since that sounds like a bug to me. And, please let us know the result so we can all learn!
- Shelley5 years ago
Post Prodigy
collinq The report name is exactly the same, I did not change it at all - no extra spaces. A change to the report itself behaves as you state - asks about the overwrite, etc. Did you try changing the Power BI dataset the report is pointing to, and then republishing? I'm really curious as to what your experience is with this specifically.
- collinq5 years ago
Super User
Hi Shelley ,
Good point - I just tested it. I duplicated my original data source. I opened PBI, changed my data source to the new copied version and then published. I went through the two URL's very closely a couple times. No difference at all.
I think you will haveto open a ticket since you either have found something unusual or you have encountered a bug of some sort. Please let us know the result though!