COGNOiSe.com - The IBM Cognos Community

IBM Cognos 8 Platform => COGNOS 8 => Report Studio => Topic started by: suhas_bhat on 19 Oct 2010 12:03:24 AM

Title: Multiple Prompt Pages.
Post by: suhas_bhat on 19 Oct 2010 12:03:24 AM
Hi,
   We have a requirement like this.
1. When a user belongs to more than 1 role display value prompt1, if a selection is made in prompt1 where the use value='A' then go to prompt2.
2. When the user belongs to only one role , skip prompt1 and if his role has a use value of 'A' then go to prompt2.
3. When the user belongs to only 1 role and the role does not have a use value of 'A' then skip both prompts  and go to the report.

Now initially we were using conditional blocks on a single prompt page but since both prompt1 and prompt2 use different queries it is not possible to add 2 queries to a single page. The properties of a page can take only either of the queries. Now we have multiple pages.

The issue we are facing is how to know if a prompt page has been loaded or not? consider scenario2 where user belongs to 1 role.In the filter of the 2nd prompt's query we have a statement like If ?param1? is null, now cognos knows prompt exists but since it does not have a value the filter expressions using the prompt parameter is not applied. What could be the solution for this.

Note: usage of default values is tricky as we are using a dimensional package,for each user the dimension is going to take a different shape..so there is no dimension value which we are sure will appear in all the cases..

Please help. ???

Title: Re: Multiple Prompt Pages.
Post by: CognosPaul on 20 Oct 2010 03:29:57 AM
I can think of a couple of possible ways to handle this.

Can you tell me how you're determining the number of roles a user has? There's a macro function that will return the roles, but they're always going to be more than one: Everyone, consumers, report viewers, query users, etc.
Title: Re: Multiple Prompt Pages.
Post by: suhas_bhat on 26 Oct 2010 12:05:15 AM
Thanks Paul, but we have decied to go for a tree prompt approach instead.