Forum Discussion
Report connected to online semantic model published over incorrect existing report
I added a few pages to an existing report called "CAS Dashboard" by downloading this file to the service, adding the pages in PBI Desktop, then republishing as the same name, intending it would replace the existing CAS Dashboard. At this point, it had seemed like it didn't work since the new pages were not showiung up in the existing report so I instead renamed it to "CAS Dashboard.", then published as new and deleted the old. I figure it's a strange bug, no problem. Now days later I find that the bug was actually that the pages of CAS Dashboard have replaced a different report in the same workspace. I now have no saved version of my "HR Dashboard" report which was totally lost when I published CAS Dashboard.
Has anyone seen this error before? Is there any version history that would allow me to get this back?
I'm really hoping I won't have to rebuild an entire report since I am convinced that this is not user-error on my part. There is no point at which I would have saved the desktop report as "HR dashboard" before publishing.
If it helps, these are separate reports, but in the same workspace, and connected to the same semantic model.
5 Replies
- tayloramy
Super User
Hi benjaminwalters,
THere's no way to get the report back :(.
I always recommend that instead of clicking the publish button from Power BI Desktop, that you save the file somewhere and then import it using the Fabric UI, this ensures that you always have a copy.
AS for why the report repalced the wrong one, that's very interesting. Fabric usually uses internal IDs to check if items are the same, not just the name, so this shouldn't happen.
Is it possible that your report was originally based on that HR report, and then modified to become the CAS report? If that is the case I could see how this might have happened.
Another great thing to do is to use GItHub or Azure DevOps and add version control to your important workspaces, this ensures that you have a version to go back to if something like this happens again.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Unfortunately I was not the original dev on this environment, so it's definitely possible the reports were created by copying/duplicating existing ones within fabric. I didn't know it was based on an internal id, as matching/not matching the report name always seemed to work as expected until now. Unfortunately, I usually keep a version on a local drive, but my org recently migrated to a new VM provider and I no longer have a saved version of every live report. Seems a cloud based repository is worth investing in for the future.
- tayloramy
Hi benjaminwalters,
I'm sorry, I have no solution for you :(.
Maybe this can be a learning moment for you and your org to help you get the support you need for a proper backup solution like Azure DevOps or GitHub?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
- DataVitalizer
Hi benjaminwalters
Power BI Service does not keep version history of reports, If a report is overwritten, there is no built‑in way to restore the previous version unless you have a saved .pbix file, a synced copy in OneDrive/SharePoint, or a backup in source control, If none of those exist, the HR Dashboard must be rebuilt from the dataset.Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
