Forum Discussion
Same report PBIX, Different Shared Dataset data sources, Duplicated Reports in workspace. Why?
Hi Anonymous
I create reports with different datasources ,and give the reports with same name .If I publish a report to service before , when I publish the second report with same name ,it will prompt “You already have a dataset named ‘test’ in Power BI. Replace this dataset ? ”
When you click “Replace” , the new will replace the original one in Service . There are no duplicate reports in my test .
In service ,it always shows only one record .
You can update the version of Power BI to latest one and try again ?
Best Regards
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous Is there any other assistance you can lend on this issue?
If Power BI Desktop does not even prompt about replace, there is nothing to be done at that level.
I am logged in on PBI Desktop and Service with same credentials, I am using the exact same PBIX file, just pointing to 2 different versions of the same Dataset, 1 is Test and 1 is Production, but I still get 2 completely seperate copies of the Report publishing into the Workspace.
This may not be an immediate issue at our company, but I can foresee this being a large scale issue for some bigger companies. If someone needed to built other customized datasets and choose to repoint an existing report like this, it will cause them to delete the old report and keep the newly published version, then causing users to lose their bookmarks, subscriptions, shared links, etc.
I can't locate any useful 3rd party tools for this either. ALM Toolkit only connects to Datasets, PBIX, and Files. Tabular Editor only conencts to Datasets as well. Since the Service lets you view settings of a Dataset and make changes to the Datasource, maybe a good option would be allowing settings to appear on a Report that lets you select another Dataset at least?
I'm beginning to think this was a huge miss from whatever Power BI development team would have covered this ability.