Problem with drill thru in Analysis Studio

[Desperado]

I have a problem in  analysis studio.  i created a report in RS and i want to make it as a drill thru report from AS. the problem is it's asking for the prompts every time ... it has to take the prompts automatically from the AS cube.

Thanks in Advance

[MFGF]

A couple of questions:

1. When you defined the drillthrough definition, did you map values from the cube to the parameters in the report you are drilling to?

2. What data type is each parameter in your target report, and what datatype is the member ID of the level you have selected to pass to each parameter - do they match? (hint - the members will display using their captions in Analysis Studio, but it's their ID [category code for a PowerCube] that gets passed through).

Best regards,

MF.

[Desperado]

1. Yes, i do specified the values that are to be mapped from the cube in drill thru definitions from tools .

2. the datatype for the parameters is char and what is member ID ??  i think we are not using any member ID .. we are directly using name ...
If we are using member ID do we need to map to the member ID in drill thru definitions ??

Thank you for the reply

[Arsenal]

While mapping in drill Thruough definition, if you set the highest level of the cube dimensions (i.e. the name of the cube dimensions itself without firther expanding the name to go down into the levels), it works fine...at least it does for me ;)

All the filters behaving as prompts in your RS report must be set to optional. Otherwise, unless every single one of those parameters is selected in AS during drill through, the prompts will come up. Hence, have the filters set to optional.

In 8.1 there is a bug wherein if you have a date filter in your RS report, then this date filter must be passed everytime when drilling through from AS to RS. In other words, a date filter in RS must always be satisfied with a parameter from AS even if it's just one whole year, like 2007, instead of say a month like July 2007

Also, such a date filter must always have an in_range condition and not a in condition

[MFGF]

Hi,

The Member ID is the unique identifier for the member on the level in the cube.  Are you using a Cognos PowerCube?  If so, the member ID is the Category Code.  You cannot see the Member IDs in Analysis Studio - just the Member Captions.  However, if you open your analysis in Report Studio, you can find the MUN (Member Unique Name) of each member.  Here is an example of a MUN from the Great Outdoors Company PowerCube for the 'Camping Equipment' product line member:
[great_outdoors_company].[Products].[Products].[Product line]->:[PC].[@MEMBER].[1]
In this case, the Member ID is 1 - the very last part of the MUN.

If I was going to pass this member to a relational report as a drillthrough value, my target report would need to filter on the Product Line Code (1), not the Product Line Name (Camping Equipment), even though Analysis Studio would display the member using its caption (Camping Equipment).

Hope that helps!

MF.

[Arsenal]

MFGF is right...depending on what the category code for the dimension(or its levels) are, appropriate filter needs to be set in RS for that query item.

besides, it's always a good idea to use a code to drill through instead of on text for performance. The easiest way to find ot what the cbe will pass on as a parameter is to open up the property sheet for the dimension's levels and looking at the category code there

[Desperado]

MF , thanks for the reply . I'll try to do it with the member ID now.

Arsenal , I don;'t want to make the prompts optional. if, i put them as optional it's working for me .... But i want them to be required parameters only and i'm using cognos 8.2 ... R there any issues with the date in 8.2 ?

[Arsenal]

I don't know about 8.2, sorry

if ur prompts are mandatory, then every single one of those prompts will need to be satisfied via AS, else the traget report will bring up the series of filters used in your target report

Also, as far as 8.1 is concerned if your cube has a Date Dimension, say named Calendar Date, and you are expecting that AS passes a value for it, then when you drop that dimension into the context area, it MUST have a valur...you cannot just drop Calendar Date dimension and expect the drill through to work, btw. So, at least the highest level(i.e. year) must be selected for it.