[Solved] Is it a rule for parameter ?

[bogdaboco]

When I use a prompt parameter in a visual element of my report, the prompt becomes obligatory?

[BIsrik]

not always...By default it is yes. u can set that to optional.

Srik

[bogdaboco]

Even if I put my prompt to optionnal, it stays obligatory. It appears to be due to the use of the prompt parameter in my report. Would it be?

[bdybldr]

You need to make sure that it's set to optional in both the prompt and the filter.

[MrO]

When I use a prompt parameter in a visual element of my report, the prompt becomes obligatory?

Yes it will always become obligatory. When processing the report CRN wants to use it, so it tries to get it.

A workaround might be setting the default value on '' (empty), so your textbox will be blank.

[Draoued]

What if you use ParamDisplayValue instead of Paramvalue ?


Please , read the board rule , and do not use upper cast for subject , like in all forums it s not needed to shout.

[bdybldr]

Bogdaboco,
Please verify that both the filter and the prompt usage properties are set to optional.  This will prevent the prompt from becoming obligatory.  I just tried it and it works.

The parameter will not display anything if the user doesn't select a value.  You can get a round this by changing your "Optional" filter to the following:

?parametername? = 'ALL' OR fieldname = 'whatever'

Then, add a static choice of 'ALL' to the prompt value box and set the default value to 'ALL'

This will work.  Good luck...hope this helps.

[bogdaboco]

Sorry for just answering now...
Both the filter and the prompt usage properties are set to optional.
I think the problem does not come from here.
I can't also use a default value to resolve it, cause I am not using a filter like  "?prompt parameter? = 'anything'", but something like that "[afield] < ?prompt parameterOne?   and  [afield] > ?prompt parameterTwo?". Thus, my two prompts associated to  ?promptparameterOne? and ?prompt parameterTwo? become required....

Does anybody know a solution?

[bdybldr]

What type of parameter are you using?  Is it a date range.  Please provide specifics about what you're trying to accomplish.

[bogdaboco]

I am using it many times, and it could any type!
MrO response woulnt be exact?

[bdybldr]

Instead of using [afield] < ?prompt parameter1? and [afield] > ?prompt parameter2?

Use this...

[afield] in_range ?prompt parameter?

Set the following properties on the prompt:
Required = no
Multiselect = no
Range = yes

Hope this helps...I know it will work

[BIsrik]

if u r having a parameter on a report column then u can set that to optional...if u r having a static values for a prompt then u cannot set that to optional..

Srik

[bdybldr]

I agree with you, Srik.  But it's not very likely that he's defining a range using a static prompt.  That's why I suggested this solution.

I believe he's using ParamDisplayValue.

bog, please keep us posted on this issue.  Thnx

[bogdaboco]

This topic was not dead!
Well, I m just trying to resuscitate it...
First, I am sorry for this very late answer, but i had to do some privileges...
I am rising up cause my problem is taking more and more criticity.

So. When I display a parameter, the associate filter becomes obligatory.
Just a few information:
I am not using ParamDisplayParameter; For two reason:
- First, I don t understand what does it change to use in  a calculated field  "paramDisplayValue
(?parameter?)" in pace of "?parameter?"...
-Secondly, when I use paramDisplayValue, a error message don t validate my calculated field, saying me that now, other part of my report contains errors. - I am using a crosstab with two requests, the second has been created by a section (section used as a header).

Well, if anybody can help me....

Thx for your responses.

I come back tomorrow.

[bdybldr]

bog,
ParamDisplayValue is appears by default when you want to display a parameter in your report layout.  If you create a detail or group calculation, it must be a query item.

What error are you getting?  Have you tried using in_range in your filter instead of >= and <=?  See the instructions posted earlier.  I think this will solve your issue.

[bogdaboco]

ParamDisplayValue is appears by default when you want to display a parameter in your report layout.

Can you give me more precisions?
How can I use it when I want to display a parameter?

[bdybldr]

Drag and drop a calculation to your report.  Select "Layout" and click "OK."

Next, click the "Parameters" tab at the bottom and select your parameter.  When you drag it to the "Expression Definition" window, it automatically appears as ParamDisplayValue("ParameterName").

[bogdaboco]

Succeded!
I couldn't use in-range instead of >= and <= , cause only one of the date limit prompts had to be obligatory.
First, I had to divide my filter in two:
Fisrt filter : promptParameterDate > lowerLimit
Second filter: promptParameterDate < upperLimit
Then, I had to display my  parameter using a layout calculation with ParamDisplayValue.

Thx to everybody, especially to bdybldr!

[bogdaboco]

When I use a prompt parameter in a visual element of my report, the prompt becomes obligatory?

[bdybldr]

Bog,
I'm glad it worked out for you.  Thanks for the update.  One question:  What is the purpose of your last post?  Is there still an issue?

[bogdaboco]

[It was just a bad manip... ;) ]