Problem with connection profile

I have created a report which uses a connection profile to connection to the database. This works fine but requires an absolute path to the connection profile file.

I wont be able to use an absolute path when I deploy the report so I wonder what the solution for this is? I have tried investigating other, similar threads but the only suggestion I saw was to have the profile name as a report parameter.

Being able to pass in the absolute path to my report would indeed be a good solution but I do not want the user to be able to choose between different environments when running the report.

Is there any other way of achieving this?

Find more posts tagged with

Comments

mwilliams

Hi Daire,

So, your issues with passing the path through a parameter is because you don't want the user to be able to choose? Am I understanding this correctly?

Daire

Yes, exactly.

I would like to use different databases for development, test and production but would like this to be transparent to the user.

Having this information in a single configuration file would be the ideal solution but I am unable to do this as the paths to this file will be different on production and development environments.

mwilliams

Daire,

Could you use a hidden parameter then?

Daire

Hi Michael,

Indeed I could. I hadnt realized that parameters could be hidden.

Thanks a lot for your help.

Daire

mwilliams

Daire,

No problem. Glad I could help.

Let us know whenever you have questions.