Cannot pass parameter from DMR Tree prompt in drill-through

[stancho]

Hi all,

I'm using Report Studio in Cognos 10.1.1.
My model is DMR. I have one Tree prompt. The data item in the query which the prompt is based on is:
Member Set, pointing to the Hierarchy level.
The tree shows the data correctly.

The filter that I put on the report table is: [Reporting Model].[Geo Dim].[Geo Hierarchy] in ?GeoParam?.

I set drill-through definition which passes this parameter based on the tree prompt. The target and the source reports are the same (just for test).
If the filter ([Reporting Model].[Geo Dim].[Geo Hierarchy] in ?GeoParam?) is enabled then the drill-through does not pass the parameter value.
If the filter is disabled the the selected parameter values is passed..

Any ideas what is wrong?

Thanks,
Stancho

[MFGF]

Hi,

I think the issue is that you have defined a detail filter (which is a relational construct) when using a dimensional package.

Remove the filter, and add either a query calculation in the rows/columns of your crosstab that uses the expression [Reporting Model].[Geo Dim].[Geo Hierarchy] -> ?GeoParam?

Or, if you are not displaying the chosen member in your crosstab, add a slicer member set to the slicer area of your query using the same expression.

Cheers!

MF.

[stancho]

Hi MFGF,

thanks for your reply.
I also tried with slicers instead of common filters but I experienced the same issue.
I managed to used relational filters because using slicers does not filter the result on database levels and returns me everything which slows down the performance. My model is DMR but not OLAP. Afaik if I have OLAP cubes I should use only dimensional filter methods like slicers, filter(), tuple()...  If I use DMR I can also relational filters which give me better performance? Am I right about it?

If I'm not displaying the chosen member in my crosstab (just filter by it) and use slicers will it have the same performance (in DMR) if I use relational filters?

I know that if I display them it will display all of the values with blank fields... Maybe this can be fixed using suppressions but what about the performance?

I will also try with what you suggest about the query calculation if I display the dimension values in the crosstab.

Thanks,
Stancho

[stancho]

btw it works for filters where the item in their query is:
Data item: [Reporting Model].[Geo Dim].[Geo Hierarchy].[Country].[Country]
and it is not member set.
But I need to be member set for TREE filters where they expect hierarchy and the user can multi-select between different levels in the hieararchy.

[stancho]

I think what is causing the issue.
It is caused because of a parameter passed from Report Studio to Framework Manager.

I have 10 different reports which uses absolutely the same structure but different tables. The tables also have absolutely the same structure.
So I made one regular dimension and one measure dimension in the presentation view in FM.
The items in these dimensional are dynamic:

Ex: #'[Consolidation View].[' + $Reports_Parameter_Map{prompt('reportNameParam','token', 'DEFAULT_DIM')} + '].[Country]'#

So different parameter values (reportNameParam) are passed from the different reports and here the calculation redirects to the proper table field.

If I remove the PARAMETER. Then passing whole hierarchy filters in Drill Through works...

Do you have any ideas is this method a good? Can you advice me on something better? Maybe I should open a new topic about this?

Thanks