Dynamic parameters on BOXI enterprise R2 - error

[cmmrfrds]

Is anybody successfully using dynamic parameters on BOXI R2?
Error we are getting.
Failed to read data from report file.
Reason: Failed to read parameter object.

Follow up question.
How do you get Crystal to do "ALL" with dynamic parameters when you don't want to pick from list.

 

[rmangel]

I have successfully used Dynamic parameters with BOXI r2. The only way I could get them to work successfully was to declare all of the parameters, dynamic and static, on the report and add a command through the database expert to define the values for your dynamic parameter.

In order to treat the 'ALL' value in a Dynamic parameter you need to define it as a static value in your select statement for your dynamic list using a union.

For future reference you should include the database type you are working with as this helps provide more complete answers.


Ray

 

[crsdev]

I am having the same problem and even the support engineers in BO couldn't help. if dynamic parameter doesn't work why it is an option, and what is ListOfValues Server used for...

rmAngel, If you have some time could you please give a procedural description

Thanks.

 

[gortuk]

I'm also having trouble with Dynamic Parameters in BOXIR2, even with SP1 and the latest hotfixes. (So far only tested Oracle data sources).

My view is that this is buggy and 'not ready for prime time', and I'm not encouraging anyone to deploy reports using this for a broad audience due to the intermittent errors.

 

[rmangel]

Crsdev,
The solution, as I have implemented it, is using BOXI r2 with an Oracle 9i database, reporting from stored procedures. I am not sure how this will work with other environments. There are also limitations with this approach so I have an open case with BO to hopefully obtain a more feasible solution. The approach I took was to remove all parameter references and look-up queries from the stored procedures and corresponding packages. The step by step process, if you already have a procedure with parameters and look-ups is as follows:
1. Make a back-up of your current package and procedure
2. Alter the original package and procedure to comment out all parameter references and procedures used as look-up values for the dynamic parameters.
3. In the Crystal Report, comment out all formula references to any parameters declared on the procedure.
4. Set the datasource location point to the modified procedure (any parameters previously declared in the procedure will be removed from the report)
5. Using the database expert remove all look-up procedures from your report and add commands for each required look-up value (Add Command is the first selection under your database connection, when expanded) – Copy your look-up SQL statements from the backup of your package and procedure
a. If you want to allow for ‘ALL’ values you would add a statement similar to this to your SQL statement:
i. union all select '~ALL' from dual
6. Recreate your parameters in Crystal Reports using the defined commands as look-up values for your dynamic parameters (if you use the same names most of your formulas will not require any changes when you remove the comments
7. Uncomment the Crystal formulas that a referencing your parameters
8. Test your report
9. Clean up your package and procedure

This process has proved to work for the reporting that I have been working with but may cause problems if your parameters must be present in the procedure. I tried many different approaches and found dynamic parameters only work as expected when all parameters either dynamic or static are removed from the procedure.

I hope this helps. Perhaps Business Objects will have a more flexible solution soon.


Ray

 

[gwsmith]

Regarding your first question:
We had the same error message when saving a Crystal Report w/ Dynamic parameters and found out that it was an edit rights issue for "Repository Root on enterprise server". We had to grant "edit" rights to specified users to allow saving or publishing reports with Dynamic / Cascading parameters.

Go to Business Views Manager and right click your enterprise server name;

A dialogue box will appear and you can then select "edit rights" for whatever user or user group(s)you are part of.

The error message certainly did not lead you to believe that it is a user rights issue so we had to do some digging to find this, but it worked for us.