Hi kumar thanks for the reply… I have doubt…
should i create the second prompt or ur referencing the first prompt??
can you throw some light on the second prompt…
wot I understood is first condition gets all the dates lesser than the selected month. and i dint understand the second one… do we need to select values in the second prompt also… can you please explain the second one plz…
thanks and regards
phani
Create a predefined condition in universe
Date <= @Prompt(‘Select Date’,‘D’,‘LOVs’,)
and
Date > Add_Months(@Prompt(‘Select Date’,‘D’,‘LOVs’,),-12)
This should solve your purpose.
You need to check the syntax for Add_Months function. But this should give the direction to follow.
Hi Kumar…
every thing is working fine but its getting multiple columns of the month…
like if i have 4 records in the month of feb its getting 4 columns in the cross tab…
i want to see all the records of the particular month in one column… do you have any idea how do i do that???
to be more clear i have four records in the month of february…
the out put is some thing like this… I want to see the feb recs in one column can you plz help me out with this…
thanks and regards
phani
Or to say this another way – your measure objects should usually USE an aggregate function, such as SUM. That is, in this case, the SELECT defined in Designer for the measure object should probably be defined as SUM(measure_column).
Well, I don’t feel as strongly about it – I’ve seen a universe where it made sense to be able to set the projection to SUM, but to retrieve the rows unsummed. The individual user might want to see the individual rows on one report but not another, and the Reporter option to Format - Table - “Avoid Duplicate Rows Aggregation” was what was needed.
However, I would concede that it might be nice for a measure to default to SUM() in the SELECT, which the designer could choose to use or not.
Hi Kumar…
I have tried the option you just mentioned…
but still i seen 3 feb columns but the values are being summed for every feb column…
by the way one more thing the months in the cross tab are records they are not individual columns…
-phani
This is one of the reasons I wish Business Objects Designer would force you to use SQL Group By statements whenever creating measures: Two Fact Tables
If the user for example wanted to see detailed transactions he/she could either pull in the Transaction ID or the designer could create a Dimension object instead of a Measure.