April 3, 2013 at 8:18 am
I spoke too soon 🙂
Phil's approach is working. But when I try to run the package thru a batch job passing variables for the template path (source) and report path (destination) the package is still referring to the values that I have set locally. I'm expecting the variables to pick up the values from the batch job. Do I have to set expressions for the source and destination properties in each of the fst?
April 3, 2013 at 8:22 am
rs80 (4/3/2013)
I spoke too soon 🙂Phil's approach is working. But when I try to run the package thru a batch job passing variables for the template path (source) and report path (destination) the package is still referring to the values that I have set locally. I'm expecting the variables to pick up the values from the batch job. Do I have to set expressions for the source and destination properties in each of the fst?
Can you provide a bit more detail about this 'batch job'? How are you calling the package and how are you passing the values to it?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 3, 2013 at 8:36 am
I'm using the DtsRunTime.package to call the package and package.Execute to run the package. In the same library, I'm using DtsRunTime.Variable to pass the variables to the package.
Does that answer your question?
April 3, 2013 at 8:44 am
rs80 (4/3/2013)
I'm using the DtsRunTime.package to call the package and package.Execute to run the package. In the same library, I'm using DtsRunTime.Variable to pass the variables to the package.Does that answer your question?
Hmm, not the answer I was expecting. Is this a C# app that is calling the package?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 3, 2013 at 8:47 am
Yes, it is.
April 3, 2013 at 8:56 am
Right - I've never done that.
It might be worth creating another thread & posting your C# snippet, if it's not too complex.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 3, 2013 at 9:07 am
Unfortunately, it is complex. And I think it's more of me not setting up the fst correctly. Do I need to set the source and destination properties as expressions assigned to variables?
April 3, 2013 at 9:10 am
rs80 (4/3/2013)
Unfortunately, it is complex. And I think it's more of me not setting up the fst correctly. Do I need to set the source and destination properties as expressions assigned to variables?
Anything you want changed at runtime should be set in expressions.
April 3, 2013 at 10:02 am
The format of the variable being passed was incorrect. The variables were set correctly with evaluate to expression. Sorry for extending this post. It was a stupid mistake 🙂
April 3, 2013 at 10:05 am
rs80 (4/3/2013)
The format of the variable being passed was incorrect. The variables were set correctly with evaluate to expression. Sorry for extending this post. It was a stupid mistake 🙂
No problem. It happens. Glad you got it all worked out. 🙂
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply