Environment variables are not included when export/import. You have to save the DSParams file in the old project. And once you create a new project by importing the .dsx file, you just have to copy the DSParams file back to your new project directory.
It will replace the existing DSParams file with the original one that you had saved. This way you will still have all your Environment variables intact.
I really don't understand why people feel the need to come and post the exact same answer that's already been posted. Sometimes multiple times.
And in case it was too subtle or something, my one word answer was (and still is, even in the quote) a URL link to a post asking the same question with an explaination of how to fix it - both the 'easy' way and the 'safe' way.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Hello every one thanks for the reply,
I manually typed in all the Userdef environmetal variables for the new project i imported. Even after doing this i see OLD parameters in the "JOBS" that are pointing to the old DNS,passwords,users...etc . Even if i change to the new one there in the job, they are going back to the OLD parameters! (Some sort of default values). I went like this
1. Exported from Producation as dsx
2. Imported to a new project in Devlopment
3. Manually typed in all the evironment variables to the Development servers.
Go to job properties of your jobs in DEV and then to "parameters" and then add the environment variables by clicking the "Add Environment Variables" button.
When you add them, check whether they show up the same default values that you assigned in the administrator.
Well, in a similar situation, I manually edited the DSParams file for the new project and copied the entries from previous project DSParams file, which was successful.
I have a related query.....if I migrate a job where I have added an environment variable,will the environment variable also be migrated along with the job? Or I have to create that environment variable separately in the target project?
I have a related query.....if I migrate a job where I have added an environment variable,will the environment variable also be migrated along with the job? Or I have to create that environment variable separately in the target project?