Hello, we have reports defined in our primary web site project, in the web.config for that project are connection strings are specified in a seperate file using the configSource attribute, for example:
<connectionStrings configSource="Config\connectionStrings.local.config" />
This works fine at runtime, the report displays the correct data, however at design time the data explorer and preview return an error that indicate it can not find the connection string. It is the standard "Unable to establish a connection to the database."
If the web.config is changed to include the connection string directly in the same file then the preview and data explorer work correctly.
Is there some way to get the reporting designer capabilities to work with connection strings specified with a configSource?
I should mention that we are using the name of the connection string on the data source.
Thanks
Joe
<connectionStrings configSource="Config\connectionStrings.local.config" />
This works fine at runtime, the report displays the correct data, however at design time the data explorer and preview return an error that indicate it can not find the connection string. It is the standard "Unable to establish a connection to the database."
If the web.config is changed to include the connection string directly in the same file then the preview and data explorer work correctly.
Is there some way to get the reporting designer capabilities to work with connection strings specified with a configSource?
I should mention that we are using the name of the connection string on the data source.
Thanks
Joe