We have report with a value prompt on the report page and its default value is controlled by a prompt macro. The report also has a Pie chart and a Crosstab both based on different queries whose data items are linked for drills.The report is based on a cube.
The observation is that when the default value for the prompt is set to a higher level of the dimension say the year level in a Time dimension and when a user selects any value from the drop down and does a drill on the pie chart categories member the drill links don't work in the Crosstab only the pie chart gets updated.
This happens only the first time a selection is made. Selecting any other value and executing a drill on the pie chart categories and then selecting the same value and then executing a similar drill does not re-produce the above error.
This also does not happen if you execute the drill without making any selections. Any selection later doesn't re-produce the error.
So basically it seems like this happens for the first selection made and when you have a higher level member set as the default through a prompt macro. Once a drill is executed and then any number of drill executions later doesn't re-produce the error.
This has been observed in a Pie - Crosstab combination and not in a Stacked Chart - Crosstab combination.
Some screenshots against Go Sales Cube to demonstrate the observation against a simmplified requirement:
First run of the report:
On selection of January 2004 from the drop down and then executing a drill up on Pie chart for January 2004:
The drill does not get reflected in the crosstab.
On selection of Q1 2004 and then executing a drill up on the Pie chart:
The drill is reflected in the crosstab.
When January 2004 is set as the default, first run of the report:
On selection of February 2004 and then executing a drill up on the pie chart:
The drill is reflected in the crosstab.
The observation is that when the default value for the prompt is set to a higher level of the dimension say the year level in a Time dimension and when a user selects any value from the drop down and does a drill on the pie chart categories member the drill links don't work in the Crosstab only the pie chart gets updated.
This happens only the first time a selection is made. Selecting any other value and executing a drill on the pie chart categories and then selecting the same value and then executing a similar drill does not re-produce the above error.
This also does not happen if you execute the drill without making any selections. Any selection later doesn't re-produce the error.
So basically it seems like this happens for the first selection made and when you have a higher level member set as the default through a prompt macro. Once a drill is executed and then any number of drill executions later doesn't re-produce the error.
This has been observed in a Pie - Crosstab combination and not in a Stacked Chart - Crosstab combination.
Some screenshots against Go Sales Cube to demonstrate the observation against a simmplified requirement:
First run of the report:
On selection of January 2004 from the drop down and then executing a drill up on Pie chart for January 2004:
The drill does not get reflected in the crosstab.
On selection of Q1 2004 and then executing a drill up on the Pie chart:
The drill is reflected in the crosstab.
When January 2004 is set as the default, first run of the report:
On selection of February 2004 and then executing a drill up on the pie chart:
The drill is reflected in the crosstab.
5 comments:
Hi Dude,
Your blog is simply awesome...
Hi Dude ,
can you please let me know how to calculate a report run-time [execution time ] in Cognos 8.4
Thanks in Advance
Hi Dilip, You can use the audit package reports that are pre-built to identify the execution time.
Here's a list of all the available audit reports:http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/index.jsp?topic=/com.ibm.swg.im.cognos.ug_cra.8.4.0.doc/ug_cra_id3354SampleAuditReports.html
Do you get this problem only when you use value prompt with prompt macros? I replicated this report with value prompt linked with package columns and it works fine for me. -- Bhavya
Hi Bhavya,
I hope you are trying this out on 10.1.1.
I will need to dig through the APAR for this defect but you can look that up on IBM Support Site.
This has been accepted as a defect by IBM. So I am guessing you are either trying this on a different version or there is some difference in the test case.
Post a Comment