Do you have multiple environments on your development server? It's a well known problem that when you right click on an element in the AOT and select Edit to launch Visual Studio, that Visual Studio itself randomly ignores provided command line and just uses the default configuration on the local machine to interact with the AOT. You could be loading a report from another instance, say your TEST environment, even though you're clicking Edit from a DEV environment. I've even seen people accidentally make changes to SSRS reports in PROD after clicking Edit in a DEV instance. One of the ways I combat this problem is to create an empty Job in the AOT of each environment named ThisIsTest and ThisIsDev, and then from the Application Explorer in Visual Studio I can easily inspect the Jobs node and be 100% certain which environment I'm interacting with, before I do anything of consequence. There is a way to bind Visual Studio to a specific environment regardless of the local client configuration and any command line sent, I believe by placing a properly named .axc file in a specific directory. I haven't done it in a while, but I'm sure I can find a link to official instructions if you would find it useful.
↧