BUG: report connected to deleted semantic model cannot be opened in PBI desktop

I've said before Microsoft need to make sure that pbix files can be opened regardless of errors that are hiding in files. There is a similar issue when opening .pbit files for semantic models that for whatever reason can't be refreshed on opening. If the refresh is cancelled, instead of just creating the new .pbix from template, a blank is created instead. This is poor design and needs rectifying

Hi JoshT, I came across the same issue today. The solution is to open the old PBIX file, but click CANCEL when you get the dialog mentioned above. Let PowerBi load, then choose File -> Open, browse to the file and open it. You will again get the same dialog, but this time you can click 'Edit' and select the semantic model you want. I suspect it isn't hanging, but the dialog is appearing in the background behind all other windows, with no way to bring it to the foreground. This behaviour happens with MANY windows in PowerBi, but every time I report it to Microsoft, I just get shrugged off. Hope that helps. Cheers, Ben.

Thanks bhalicki, that does indeed work. Evidently there's a stategic issue in the way that PBI desktop loads info in when opened since it behaves differently when opening a file already open. Not surprised nothing's been done about it - they should be paying us to do all this QA work! At least the solution is here for anyone elsee running into this issue

Tip of the iceberg. I think there is a fundamental issue in the way PowerBi handles it's dialogs. I frequently experience an issue where the authentication window appears behind all other windows, with no way to bring it to the front. The app is rendered useless and the only way is to ctrl+alt+del. Happens in powerquery too, especially with a larger dataset and slower connection - some dialogs will take forever to open and when they do load, they load behind other windows. As for the payment of QA.. I 100% agree. I lose hours and hours of my day, which I cannot charge to clients, to work with MS support teams, replicating issues, only to be told it's by design, a known limitation, or not implemented feature. The majority of my work involves developing dashboards for clients using PowerBi, and I am ready to walk away from the product - just not worth it anymore.