Multi Valued Dynamic Parameters Not Working

[organickarma]

Hi,

I am currently developing reports in CRXIR2 using a SQL Server 2005 DB with an ODBC connection.

The issue I am facing is that I have a report with a total of 38 parameters. The main report acts as a shell to prompt the user for parameters and the actual data is pulled in by a sub report.Six of these parameters are dynamic parameters (LOV) that are populated by five separate command objects.

The report runs fine on my desktop but the moment we try to publish it to Infoview we get an error message that reads

Failed to read parameter object.

Then I changed all the parameters to static and ran the report and it seemed to work fine, both on my desktop and CE

I need to retain the dynamic nature of these parameters without the errors popping up.

Any help is greatly appreciated.

Thanks!

 

[Turkbear]

Hi,
A report that runs fine on a local PC but has issues when published is usually the result of a lack of permissions granted to the CR Server/BOE services that allow them to access either the data or its location. Check those on your server and see if it helps.





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[organickarma]

Thanks Turk, I had the admin check the rights and he said that could not be the issue since we have many other reports using the exact same structure with dynamic prompts working fine.

I tried removing all dynamic prompts and adding them back one by one. The error returns as soon as I add the first dynamic parameter.

I'm devoid of ideas now!

 

[Turkbear]

Hi,
Reconfirm with your Admin that by

using the exact same structure

he means all parts of the process - same user/pass in the report, same database and tables,same parameter source(s) etc..

Just to be sure...Things that look alike may not be.





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[organickarma]

Ok, just so we can put this to rest... I removed all command objects used to populate the parameters and re added them one by one and linked them back to their respective parameters and was able to publish the report.

No idea why this worked but makes me think CR somehow embeds the DB information into the command objects and since these reports were developed in a different environment it would seem like the db details for that environment were associated with the parameter commands...I might be talking complete non sense, so if somebody has a more educated response than me
please do post it here...I would like to know the logic behind this.

 

[Turkbear]

Hi,
commands are datasource-specific and need to be reset if the datasoure for them changes using the Set Database Location option.





To Paraphrase:"The Help you get is proportional to the Help you give.."