Bonediggler1
Technical User
Hi
I have two variables, "BEGDATE" and "ENDDATE" scoped at the package level. They are defined via input boxes prompted in a script task.
The next component is a file system task (doesn't use the variables) followed by a data flow task where the variables are used to define date paramters for a data pull from an Oracle back end.
The final step is another file system task which copies the output file to a new location with a new name, using these variables in the name...i.e. "File_Name_" + @[USER::BEGDATE] + "_" + @[USER::ENDDATE] + ".XLS".
HOWEVER-- by this time the variables have lost their value(s) and the file name comes out as "File_Name_.xls".
Why is this happening when they are scoped at the package level??
Thank you!
I have two variables, "BEGDATE" and "ENDDATE" scoped at the package level. They are defined via input boxes prompted in a script task.
The next component is a file system task (doesn't use the variables) followed by a data flow task where the variables are used to define date paramters for a data pull from an Oracle back end.
The final step is another file system task which copies the output file to a new location with a new name, using these variables in the name...i.e. "File_Name_" + @[USER::BEGDATE] + "_" + @[USER::ENDDATE] + ".XLS".
HOWEVER-- by this time the variables have lost their value(s) and the file name comes out as "File_Name_.xls".
Why is this happening when they are scoped at the package level??
Thank you!