If you are unable to create a new account, please email support@bspsoftware.com

 

Tree Prompt Default Selections not displaying as expected in ParamDisplay

Started by dekovite, 11 Mar 2014 11:28:47 AM

Previous topic - Next topic

dekovite

Hi, looking for some advice about what I believe is strange behaviour with a tree prompt with Default Selections.

The report is built against a CUBE, and to assist the end user, we have selected some Default selections in a Tree Prompt.  The Data runs as expected using the selections, and on the report page we also have a header summary to display what was selected.

If the tree prompt remains closed when the report is run, the ParamDisplay appears as follows :

[CUBE_SWSC].[Product].[Product].[Division]->:[PC].[@MEMBER].[26], [CUBE_SWSC].[Product].[Product].[Division]->:[PC].[@MEMBER].[75], [CUBE_SWSC].[Product].[Product].[Domain Name]->:[PC].[@MEMBER].[DomainName]

However, if you expand the prompt before running the report, this is replaced with the expected name values for the items.

I've set the prompt to Pre-Populate and added 4 to the Pre-populate levels thinking this would fix it, but no joy.

The ParamDisplay uses some Case statements depending on the report selected, it fills based on a parameter, but I don't think this is the problem as when the tree is expanded, it works as expected.

Any suggestions for how to correct the problem, preferably without asking the user to always expand the tree ?

Thanks

Ammus1234

Are you using a report expression in the header? I have a similar report which display correctly.
Which version of cognos are you using?

MFGF

Meep!

dekovite

The exact contents of the Report Expression is as follows :

CASE
WHEN (ParamValue('pType') = 'Replayout1') THEN (ParamDisplayValue ('pReptype1'))
WHEN (ParamValue('pType') = 'Replayout2') THEN (ParamDisplayValue('pReptype2'))
WHEN (ParamValue('pType') = 'Replayout3') THEN (ParamDisplayValue('pReptype3'))
ELSE ParamDisplayValue('Reptype4')
END

We are using 10.2 and will shortly be upgrading to 10.2.1.2, so have access to a test system on that version, but it still does the same thing when I tried it yesterday.

As mentioned previously, if you expand the tree, it all works fine  :-\

naydog