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 issue - Conditional Blocks

Started by cognosun, 23 Sep 2010 07:00:30 AM

Previous topic - Next topic

cognosun

We are using 8.4 , Oracle 10.2

We have a Report Studio report which has drill through option to a child report.

Child report has 'conditional blocks' in it.

The issue we are facing is, if we click on a link ( in parent report) ideally it should give us respective conditional block's data ( in child report )...but here what ever parent link we select ( from parent reprot ) , we are getting all the blocks from child report......this is not happening in one envrionment, but occuring in another environment.

Can anyone help.

RAJKASSEN

What do you mean by one environment to another (test and prod)?

cognosun

Yeah...in development and tesing environmetns it is working fine...but in Production environment it is behaving in the above way.

All the 3 environments carry same  8.4 version.

MFGF

How are the conditional blocks controlled? Are you passing any kind of item or parameter from the parent report which is used in the conditional display?  If so, have you made sure that both the parent and child report are the current versions in the Live environment?

MF.
Meep!

cognosun

I'm passing Parameter to the Child report.

Parent and child possess same version.

RiesBruins

How about the user perissions are they also the same as in the test enviroments?

cognosun


IceTea

What you can do to do a check what's going on is to add the Parameters and ParameterValues in your child-report-output i.e. as singletons. So you can see if the parameters are filled correctly.

MFGF

Quote from: IceTea on 04 Oct 2010 03:44:49 AM
What you can do to do a check what's going on is to add the Parameters and ParameterValues in your child-report-output i.e. as singletons. So you can see if the parameters are filled correctly.

Good advice! :)  If you struggle with singletons, use Layout Calculations and display both Paramvalue() and ParamDisplayValue() for each parameter.
Meep!

cognosun

This issue somehow resolved when we sent 3 parameters to the child report, from Parent report ( before it was 2 parameters).

But somehow this is not the issue with one environment i.e. child report worked fine even though we sent only 2 parameters there.... :)