I think the only way around this is to manage multiple connections on each server. So for instance, if I have a dev database and a prod database, I would need the dev workbook to already point to pro…

Also, if we did have productions for Prod/Dev versions of the same environment, that would require opening up firewalls that we currently do not allow to happen in our systems. For us, pointing a Dev…

What's really odd is that when you export a workbook, you have the option to "not include Connection information" but then you do the import and it's clearly being included regard…

I know this an old item, but what if you have a semantic model in Dev and you want to promote to a higher environment? It seems like then your connection information would potentially break as well? …

I also noticed we have this in our odbc.ini file. I don't know if anything here needs to updated or not.