Crystal Enterprise 9.0 ePortfolio Parameter Issue

[gaishan]

This is using Crystal Enterprise 9.

I have a parameter field that has for it's values 4 different numbers each with their own description. When a user chooses to schedule the report in ePortfolio and they choose the option they want for that parameter field and hit add it puts the description in rather than the value. If I have the value and description chosen to show then it will put both into the added value. This causes the scheduled reports to fail as they are not getting proper values (just the number). When just choosing view instead of schedule it works properly in ePortfolio.

Any help would be appreciated.

 

[synapsevampire]

Descriptions aren't passed when selected.

In fact you cannot obtain them from a formula.

So try to think of another reason for your failure, possibly pointing to the wrong database.

-k

 

[gaishan]

Unfortunately it's exactly what's happening. The description of the parameter is what is being passed because that is what is showing in ePortfolio. The parameter itself is a Crystal only parameter which gets it's default values set inside the Crystal report. So for example when a user attempts to schedule the parameter is as follows -

Age Parameter

value description
17 17 and Under
18 18 to 20
21 21 and Over
0 All Ages

The parameter when scheduling shows 17 and Under in the drop down. When pressing the add button it puts the 17 and Under into the value rather than 17.

If I use view rather than schedule, the 17 is used rather than 17 and Under. The Crystal manager operates correctly as well.

 

[synapsevampire]

Never heard of Crystal using a description, and the behavior you mention is the proper behavior when you have selected prompt with description. When you add it, it adds the description, but what is passed is different.

You've presented no evidence of this being the case.

What you need to do is test.

So once you've chosen, check the Database->Show SQL Query within Crystal Reports, and add the following to the report header:

join({?MyParameter},",")

Now it will show you what was chosen and being passed.

It's possible what you state is happening, but from what you've used to test, you couldn't possibly know.

You can probably also check what was passed on the database side, but I can't assist you there until you share what database is being used. Please remember to post basic technical information.

If you've figured out a means to pass descriptions you will delight many people here, including myelf, as that has been something sorely missing, but at this stage you're simply making inaccurate assumptions based on the parameter screen.

-k