prompts and report list on same report page - need to keep list from running 1st

[maxchuie]

I have prompts and page on same report page.
I need to have the reports not run until the prompts are selected. is there a way to do this within the same report page


thx

[navissar]

I wonder, if that's what you need, why not use a prompt page?
Anyway, create a variable that checks if parameters are all filled, and make it a render variable for the list - that'll do it.

[bdbits]

It's a bother to have a prompt page when you have in-line prompts. Just another thing to maintain and keep in sync with your main page, especially if your page has a lot of carefully positioned and formatted elements and you want the consumer's experience consistent, not having something looking different the first time versus selecting new prompt values and rerunning.

It's very easy to do this.

• Like Nimrod said, first create a boolean variable to check if the required parameters are not null. For example: ParamValue('pMyFirstParameter') is not null and ParamValue('pMySecondParameter') is not null
• On your report page, select the data container you want to prevent running.
• On the properties, find the "Conditional" section and click the button to the right of Render Variable.
• Select your variable from the dropdown list.
• In the Render For box, check "Yes" and click OK.

So when the report first runs, the parameters will be null. This will make the value of the variable "No". Since that means the data container will not render, it will not run. Now when the user selects a new parameter(s) and submits (or it autosubmits), the value of the variable will change to "Yes". The report must then be rendered, so it will run with the selected values.

Hope you can follow this alright and it works for you, maxchuie.

[navissar]

Hi bdbits,
Of course it's a hassle to maintain prompts inline as well as in prompt pages. That's why I use reference objects. You create your prompts once, put them in a named block, and just drag in a reference to this block on the second page. Hassle free, variables maintenance free. On some projects I even go the extra mile and just create one report with all possible prompts, reference it on every report (overriding irrelevant prompts) and boom: I have a single point of reference for all prompts.  8)

[Francis aka khayman]

i once have an a  hole boss. No prompt page he says... then went on to describe the report functioning exactly how a report with prompt page functions.   :-\

[maxchuie]

thanks all yes mine doe snot want a prompt page he wants them to be able to select prompts at any time.

[bdbits]

Nimrod - yeah I can see that working. I actually use layout component references a lot for things common across my reports, but never thought much about using it within the same report. Interesting. I think I will still prefer to skip the prompt page and use render variables as needed, it is just more intuitive to me I guess. Six of one, half a dozen of the other. Cognos can accomodate everybody.  8)

khayman - steer your boss into stating his requirements and leaving implementation details to you. Then use the prompt page. :)

[bdbits]

sorry for the double posting - maxchuie did you try any of the suggestions? are things working the way you want now?