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

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

How to filter data showing up on prompt

Started by _jl_, 14 Jun 2013 02:36:01 AM

Previous topic - Next topic

_jl_

Hi,

The problem is concerning delivery data. There are tons of customer names coming from the source. If I make a prompt page where user can choose which customer's data he want's to see there are a really long list of different customer's names...

How can I restrict the data coming to the prompt so that it will only show the customer names to which has been delivered something over the last 12 months or so?

I have a measure 'Completed' telling the volume as well as object for 'Last 12 months'.

Thanks,
jl

blom0344

Tune the prompt query with the proper filter on the query itself. This will restrict the set of Customers returned. You can also use a system of Cascading prompts where the user will make a pre-selection in the first prompt (like selection the period as number of months) and then return the list of customers in a second prompt based on input from the first.  Lot's of possibilities, Cognos really shines here..

_jl_

Ok, yes, I just realized I was able to filter the prompt itself...
So now i got the filters:
[Completed] > 0
and
caption ([Year]) >= ('2013')

So it brings me the list of customer names to whom something has been delivered in this year. But I dont get it how can I use that "Last 12 Months" object in the same way so it would bring me the data based on that??

_jl_

#3
Under that "Last 12 Months" object there's "Month" which shows those actual last 12 months. So if I drag that 'Month' to Prompt Page's Data Item's list and set the Detail Filter: '[Month] is not null', it shows me a list of Customer Names. More than just when there was 'caption ([Year]) >= ('2013')' but not all of Customers though. Guess that's correct then?? :) Not sure if best option though??

blom0344

Using that item possibly intrduces a join in the SQL acting as a filter. You are aware you can check the proposed SQL to verify?