Maybe someone can assist me in solving the following Active Report requirement:
The active report consists of following objects:
1) A data button bar where the user can select the product lines
2) A slider where the user can select the year
The report should display a crosstab for
a) the selected product line and with a data iterator
b) its children
filtered for the selected year
When I select "Camping Equipment" and "2005" I want to display "Camping Equimpent", "Cooking Gear", "Sleeping Bags", ... for "2005" in the crosstab.
Pls. see attached report spec. based on Great Outdoors Company Cube, Cognos 10.1.1.
Problems in the sample report attached:
1) When I select a Product Line in the data button bar, the first dot in the iterator is not checked.
2) What do I have to change, so that not only the children of the selected product lines are displayed in the crosstab, but also the selected product line itself.
3) Is the design approach the correct one ?
Maybe someone could help.
Pinned topic Active Report - design help urgently required
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-03T19:54:19Z at 2012-10-03T19:54:19Z by DanielWagemann
Re: Active Report - design help urgently required2012-10-02T13:35:33ZThis is the accepted answer. This is the accepted answer.Here is the spec against my 10.1.1 Great Outdoors cube. You may need to do a quick find and replace on the cube name.
I had to drop the iterator into the deck definition. This means you will get one itrator object for each Product line. I am not overly happy with that.
SystemAdmin 110000D4XK1959 Posts
Re: Active Report - design help urgently required2012-10-03T19:21:02ZThis is the accepted answer. This is the accepted answer.
- DanielWagemann 2700058MAJ
Thank you, that's exactly what I need ! Good idea to use a union function ;-)
Why are you not happy to place the iterator inside the data deck ? Any drawbacks ?
Re: Active Report - design help urgently required2012-10-03T19:54:19ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
The drawback of having the iterator within the deck is that it creates one iterator object per card. I should have been able to create 1 iterator and link it via the Master-Detail from the first button bar, but for some reason the product lost the context of the slice.
Hopefully you do not have too many cards and the MHT does not become bloated.