Forum Discussion
Migrating a tabular model and reconnecting Power BI
Gregs138, I think this is a miss that needs to be addressed. Right now AS based data sets are hard-wired into the physical instance which makes it difficult to promote things from Dev to Test to Prod.
Hopefully it will get addressed soon.
If you use the Power BI Desktop to author these reports connecting live to AS and publish it to Power BI Service, you should be able to change the server name from the Power BI Desktop tool.
It works if you have a couple of users and they know what they are doing, but if we had hundreds of users with thousands of personalized dashboards and reports and we decided to move our AS with let's say Finance, Sales, HR, R&D, Planning, Pricing, Vendor Managmeent and a bunch of other models to a different IP address (or if we decided to move our models to a bunch of different servers because of model size growth) telling users to go ahead and change that in their Power BI Desktop to point to the new server and then redeploy everything would probably not be a good idea.
Andre, that is exactly my point. with 3-10 users no big deal. To scale this to an enterprise level it certainly is a legitimate design problem. I think my idea of "deploy the newest version of a content pack connected to the new tabular model on the new server hardware" is a good work around if the situation were real today, but a model built in power BI should have some way to modify/alter the data connection just like the desktop designer does imo.
