Migrating a tabular model and reconnecting Power BI

Hey Greg,

Not a definitive answer here, but we just had to go through messing around with the tabular model today as we had a POC set up and the client asked to us to delete all data prior to the engagement. With the caveat of, "please keep the reports". 

So, I'll start with our current solution, then do a high level of what we tested.

Solution: Re-create the reports in PBI Desktop to have a hard copy. The removal of the AS connector didn't seem to delete the reports in PBI Desktop, and we were able to re-connect. (We did not cover every single scenerio, so be cautious). My "for sure" solution is I backed up the reports by screen shoting them all. - I really, really don't like this solution.

Scenerio/Testing: (we tested on a different AS model)

All POC reports were created in PowerBI.com using the SSAS connector.

All testing we did around removing the AS tabular model and trying to reconnect to powerbi.com failed. The service was never able to resolve the reports to the existing connection so there was no way to recover the reports., we had to create another dataset which doesn't help at all. Service = dead end currently.

We created a connection to the SSAS model in the PBI Desktop, created reports, saved the file. removed the model (detached-offlined), opened the desktop designer (which failed as expected) closed it, put the model back, opened the designer and it resolved with the reports coming back.

What I fear here, and we didn't test, is in the future the server will be different when we turn on the AS instance in the future, so i don't know if my reports will resolve - thus the screenshots. It may just be caching the connection in the Desktop and reconnecting differently.

Hope this helps, although I don't see a clear answer to this right now.