File Connector w/ Execute Package Task Expression Bug?

Hi.

We are trying to 'drive' the list of package to be executed by placing the package file names in an external datasource (a flat file). The idea being that the end user can modify the file to switch on / off the packages to execute or modify the order they are executed without having to use the Visual Studio IDE.

We've gone about this by the following:

1)   Read the external datasource into a recordset using a dataflow task.
2)   Used a foreach loop to iterate the recordset, saving the value in a package scope variable so we can use it later on.
3)   Within the loop there is a Execute Package Task which has a file based connector that tells it where to find the package.

Within the file connection object we have set an expression that sets the connection string to be the variable described in 2) above.

When executed the expression is not set to the variable but is left in its default state and the Execute Package Task throws an exception that it can not find the package to execute. I have used the same file connector with a File System Task instead and it works as expected, so it appears to be only when used with the Execute Package Task.

Can anyone confirm if this is a known bug and if so, are there any work arounds

Thanks

Steve

Answer this question

File Connector w/ Execute Package Task Expression Bug?

Koni
Apologies Kirk.

I thought my dev machine was running the latest, but it turns out that it's an older release. I'll install the June CTP and hopefully that will fix it.

Thanks for your prompt replies anyway.

Steve
智慧机器
Wow, really odd. Please file a bug at beta place.
sam2006
Works perfectly in June CTP.

Thanks for your help.

Steve
Kent Ogletree
Steve, this is interesting. Are you able to make it work outside the loop with just the execute package task and the connection withthe property expression
ken016
Ah! I love to hear that... :)
Thanks,
rana das
Steve, just built a package that has an execute package task in it that uses a connection manager with an expression on the connection string property and was unable to reproduce the problem. What build are you on June CTP
Lonny R
I've found a temporary workaround.

If I place a file system task as the first task in the for loop and then call the execute package task the expression will have been correctly set.

It's not ideal, but at least it lets me move forward.
novicestudent
No problem, let me know how it turns out with June CTP.
Thanks,
K
File Connector w/ Execute Package Task Expression Bug?

Answer this question