Hi, Is there a way to materialize environment variables (those variables defined in administrator for a project ) in a transformation stage? I see the ability to materialize local variables. I'm looking to place the value of these variables as actual data in a sequential file.
I'm not really set on using a transformation stage if there is some other way to do this. Example would be a environment variable with the database name in it.
I'm not at a workstation where I can test this now, but if you cannot use the user-defined variables directly, then you declare them as part of your job parameters, call them with a value of "$PROJDEF" and use them in the transform stage.
Thanks for the response.. Yes, that is what I was trying. Including them as a job parameter, for example Job parameter $env with a default value of $PROJDEF. Then I'm trying to use $env in the transform.. that is where I'm not able to materialize to the actual value. Thanks.
You need to have created them in the project via the Administrator first, did you do so? If you did, you'd need to expand a teeny bit on the problem you are having. Saying "not able to materialize" doesn't really give us much to go on.
-craig
"You can never have too many knives" -- Logan Nine Fingers
I believe you are looking for function: GetEnvironment, because you cannot use Environment Variables directly in a transformer like the job parameter. You have to call the function to return the value for you.
You can if they are defined in the project and then passed in as job parameters. You would need to use the function noted for environment variables not defined / passed in.
-craig
"You can never have too many knives" -- Logan Nine Fingers
</a>