Skip to Content

BI Crystal Enterprise Publication fails

Hi All,

Can you help?

When packaging a number of Crystal reports as a publication, the publication fails with error :

Parameter field(s): {XXXXXXI} are in use and require a value. (CRS 300014) (CRS 300002)

Document XXXXXXX failed for the following users:XXXXXXXX These users had the following profile values:[No profile values]

Each of the Crystal reports contain hidden Parameters, which are referenced in formulas within the reports, with the purpose of hiding data in particular sections of the reports.

Each report, runs OK when viewed in isolation and the report produces the correct output, it is only when the reports are packaged in a publication that they fail.

My understanding is that for Crystal Report publications the publication is expecting the parameter values to be populated via a user/group profile within the personalization settings of the publication.

I have tried the following:

1. I changed parameters in one of the underlying reports from 'hidden' to 'prompt to user'

2. I created a simple user profile in the CMC for one user account and assigned a profile value relevant to the parameter in the report. - Note I am not a BO administrator but was able to do this in a test environment.

3. I created a new publication with just one Crystal Report and set the default parameter values via personalization settings. The publication runs and I receive the correct report output.

4. I then tried to add an additional Crystal report to the new publication and publication fails with a similar error.

5. The additional crystal report that I added to the publication also contains parameters, however this parameter will have a value different to the first parameter set in the user profile value.

Is it possible to have multiple parameters in crystal reports and package the reports in a publication when each report has difference parameters.

How do you specify multiple parameter values in a profile and link the profile value to the report parameter

Does anyone have documeted steps?

Thank you.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Nov 07, 2017 at 06:37 PM

    Did you check this KB?

    2249149 - In Crystal Reports for Enterprise, error appears when scheduling a report with 'Hidden Prompt'.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 07, 2017 at 09:01 PM

    Are these "classic" Crystal or Crystal for Enterprise (CRE) reports?

    One other option for bursting reports is to use another report to provide the bursting information instead of using profiles. I have used this successfully with both types of reports.

    Basically what you do is create a report that has the following types of information:

    - One column for each of the field value(s) that you want to use for bursting the reports.
    - If you're emailing reports, the email address to send each set of burst reports to.
    - One column for each of the parameter values that you'll use in the reports.

    For each subreport parameter, I would also create a corresponding parameter in the main report and use the Linking Expert to link the two parameters by selecting each parameter from the main report in the top left, moving them to the top right, unchecking "Select data in subreport based on field:" on the bottom right, and, finally, selecting the subreport parameter from the drop-down on the bottom left. By having the parameters in the main report instead of just the subreports, it should make it so that the publication can "see" them.

    You'll then have the info you need to match up the values you need for parameters when configuring the publication.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Dell,

      Many thanks for you reply, much appreciated.

      My query relates to Crystal Enterprise.

      I haven't used parameters in this manner before - i.e. using another report to provide the bursting information.

      I will review your response and see if I it works for my problem.