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

Drill through filter

Started by diasbrad, 03 Mar 2015 03:31:21 AM

Previous topic - Next topic

diasbrad

Hi Friends,

I have facing a drill through problem.

Situation.

I have a Summary report and a Detail report.

We have a product filter which is having a hierarchy of 5 level.

When we filter the product at the 3 level the parent report runs fine.

But when we pass the parameter value of product of 3 level to the detail report it does not filter the data.

Can anyone advise what do I need to do here to fix this.

Thanks in advance
Brad


MFGF

Quote from: diasbrad on 03 Mar 2015 03:31:21 AM
Hi Friends,

I have facing a drill through problem.

Situation.

I have a Summary report and a Detail report.

We have a product filter which is having a hierarchy of 5 level.

When we filter the product at the 3 level the parent report runs fine.

But when we pass the parameter value of product of 3 level to the detail report it does not filter the data.

Can anyone advise what do I need to do here to fix this.

Thanks in advance
Brad

I assume it's a dimensional package since you're referring to levels? Can you tell us what the expression in the target report is, and how you have set up your drill-through definition?

MF.
Meep!

diasbrad

Hi MF,

The package has 2 models created in it Relational and Dimensional.

The report has been created using the Relational Model.

Only to filter the data we are using the Dimensional Model.

We have set up the Drill through in the following way.

Please see attached print screen for the Drill through definition and the filter in the child report.

Thanks
Brad



Robl

So you're trying to pass a relational item "model" as a filter to a dimensional report?

diasbrad

Rob,

Both the summary report and detail Report are created using the Relation Model. Dimensional Fields are only used in the Filter in both the report.

The Dimensional Model and the Relational Model are connected. But I do not know how they are joined because I do not have access to the Frame Work Model.

Thanks
Brad

Robl

You mean it's a relational model with a dmr modelled dimension?

diasbrad


Robl

Well, it looks like you're passing the MUN.
So you should probably be using the passes MUN as a slicer set.


diasbrad

Thanks Rob for the reply . Could you please guide me how do I apply the slicer filter with an example.

I have not used this option.

Thanks
Brad

MFGF

Quote from: diasbrad on 03 Mar 2015 06:50:35 AM
Yes that is correct.
Hi,

You're mixing relational and DMR dimensional objects in the same query of the same report? Why would you do this? You're creating a world of pain for yourself here. Either use relational or dimensional items in your query, but not both. If you're using a dimensional paradigm, detail filters are not a good idea - only in a relational paradigm. You appear to be using a dimensional item in a detail filter of a relational report - that is so wrong on so many levels :)

Can you explain to us what the requirement is - we might be able to suggest a way of writing the report using either only-relational or only-dimensional items that works.

MF.
Meep!

diasbrad

Thanks MF for the reply.

It is the business requirement of the user.

The user require a tree filter for Product where they have the flexibility for select information at top level and lower level.

From  example

- Prod 1  (Level 1)
  -Prod 1.1 (Level 2)
   +Prod 1.1.1 (Level 3)
   +Prod 1.1.2
   +Prod 1.1.3

In the above example

1) The user select Level 1 Prod 1 he will get the report for all product at level 1
2) The user select Level 2 he will get the report at for the sub level.

Is there a way where I can replicate this in the same way through Relational Model.

Thanks
Brad


Robl

I have used relational models with duplicate dims modelled in a DMR style to allow me to use tree prompts or drill downs.
It's not the most efficient method of doing things, but it does offer a certain amount of added functionality at the cost of a bit of performance.

Relational/DMR hybrid reporting can work; you just need to be aware of what you're doing.

For the original problem.
Try creating a new drill through to a blank report, but on the blank report add a couple of paramvalue report items so you can actually see the value that's being passed.
Then you can see about adding it as a detail filter or slice.

diasbrad

Thanks Rob,

I am currently trying out the same way as you mentioned just trying to construct the report part by part to find out where the actual defect lies.

Will update if I get any solution to this issue.

Thanks
Brad