Why is filter on report page not reflected while updating value prompt

[inu]

HI
I developed a report with a value prompt (single-select) on prompt page, Automatically a detail filter is created on report page ,while bulding prompt.
On further , requirement changed from single select to multiple select , i changed the property of value prompt as multi-select to 'Yes'.
Now this change should reflect the created filter on report page or not. From my point of view it should reflect, because while creating value prompt, automatically filter is created, so even in this case , it should change the filter code(from 'equal' operator to 'in' operator).
But i m not seeing any effect on filter, i have to change the filter manually.
Please justify the point.

Regards
Inam

[BigChris]

What you're seeing is absolutely what's expected. If the filter was an "in" filter in the first place the prompt would have been a multiple select...but changing the prompt after the event will not change the filter.

[inu]

What you're seeing is absolutely what's expected. If the filter was an "in" filter in the first place the prompt would have been a multiple select...but changing the prompt after the event will not change the filter.

Why it is not reflected, if many prompts are there, and each and every prompt is modified , in the sense , changing property form single select to multiple select or vice versa. then i will have to first find the corresponding filter and manually modify the same.
Isn't it something out of sphere of the user friendly application.

Cheers!
Inam

[CognosPaul]

There is no direct connection between the prompt and a filter.

The prompt object simply supplies a value to a parameter. There are a few ways to supply values to parameters, prompts, drillthroughs, or HTML items. Once the page starts running, it checks for any calls to those parameters. Those calls can be in report expressions, data items, filters, joins in the framework, session parameters, prompts in the data source connection, or even variables in certain data sources.

Filters can also have many different appearances:
[Namespace].[Filter]
[Data Item] = ?param?
[Data Item] = #prompt('param')#
[Data Item] = #sq(promptmany('param'))#
#prompt('FilterType','token')#
#prompt('Month','int','1=1','[Month] = ')#
[Data Item] in {select t.field from table t where t.key in (#prompt('FilterSet','token')#)}

I have an intense distrust of wizards and their hats. What you're asking for MIGHT work on the second example I gave, but even then the same parameter might be used in a different way in a different query.

Another way might be to use generated prompts. Those will build the prompt control at run time based on how the parameter is being used.