Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Connection manager doesn't keep the default ConnectonString value when I set it up with an expression.

$
0
0

Hello,

I'm trying to set up dynamically the connection managers of my packages.

So, I read the value for the ConnectonString from a .xml confinguration file into a variable, then trough an expression I set the value of the ConnectionString for the connection manager and it works fine.

The problem is: for some connection managers when I set the value of the field *Expressions* (specifically *ConnectionString* inside *Expressions*) in the Properties window and save the file it (BIDS) automatically deletes the default value that I had for the *ConnectionString* property (this is the other *ConnectionString* field, the default one which is not related to *Expressions*)

So, it's like if I just can have one value for *ConnectionString* either the hard-coded default value for the connection or the dynamically set up through the variable in expressions.

Thanks in advance for your help.

J.O.

---------------------- some more specificities ------------------

In my main package the FILE type connections work fine -> keep both values, but the OLEDB type connections don't -> either one or the other.

In secondary packages neither FILE nor OLEDB work. The OLEDB connections erase the default connection string the moment I set it up through the expression. And the FILE connections do something weird, my dynamic expression is of the sort: @[User::v_FilePath]+ "File.dtsx", well when I save this it replaces the default connection string that I had with "File.dtsx".

I read the configuration values from a .xml file in the main package and roll the variables downwards to the secondary packages as needed.

I'm using Visual Studio 2008.

------------------------------------------------------------------


Viewing all articles
Browse latest Browse all 24688

Trending Articles