SOLVED: Prompt selection change ignored in filter/slicer

[prikala]

(Cognos Analytics 11.0.10, Run with full interactivity, DMR-DQM package as source)

Has anyone seen this kind of problem:
I have some reports that have a value prompt embedded in the report page, to use selection users must press Prompt button (Finish).

When a different member is selected and promt button is pressed, report expression using ParamDisplayValue shows the selected value but the data itself is not filtered or sliced (tried both) according to the selection.
Data is updated only when users uses the "Refresh" icon or selects something from a prompt that works.

The weird thing is, this problem is only with a couple of prompts. There are similar prompts in the same report that are workin ok.
It seems the prompt type does not matter (tried Tree and different value prompt types).

If I move the prompts to a separet prompt page, everything works. Unfortunately that is not accepted as solution.

(unfortunately I can not provide you the report xml)

[MFGF]

(Cognos Analytics 11.0.10, Run with full interactivity, DMR-DQM package as source)

Has anyone seen this kind of problem:
I have some reports that have a value prompt embedded in the report page, to use selection users must press Prompt button (Finish).

When a different member is selected and promt button is pressed, report expression using ParamDisplayValue shows the selected value but the data itself is not filtered or sliced (tried both) according to the selection.
Data is updated only when users uses the "Refresh" icon or selects something from a prompt that works.

The weird thing is, this problem is only with a couple of prompts. There are similar prompts in the same report that are workin ok.
It seems the prompt type does not matter (tried Tree and different value prompt types).

If I move the prompts to a separet prompt page, everything works. Unfortunately that is not accepted as solution.

(unfortunately I can not provide you the report xml)

I haven't seen any issues like this, personally. Is this something you can mock up using the samples? GO Sales (analysis), for example, is DMR DQM. If you can duplicate the issue in the samples, I can test in my 11.0.12 instance.

Cheers!

MF.

[prikala]

Unfortunately the sampeles are not installed in this environment.

It seems the reason and a seemingly working workaround was found.

The problem occurs when
- report contains master detail structure, the main content (using the
  problematic parameter) is provided by the detail query
- prompts are embedded in the report page
- master detail relation is using a parameter in the detail side (not the
  problematic one. This is used in an item that is used as a slicer)

When detail query and master-detail link is modified to use only query
items, the problem is gone.

I still believe using a parameter to "drive" the detail side of master detail
is not totally wrong as everything works if prompts are placed on a separate
prompt page....