Problems Creating Reports
The topics in this section document problems you may
encounter when creating reports.
- Division by Zero Operation Appears Differently in Lists and Crosstabs
If you have a list that accesses a relational data source, a calculation containing a division by zero operation appears as a null value, such as an empty cell. In a crosstab, the division by zero operation appears as /0. - Application Error Appears When Upgrading a Report
When upgrading a report, the following error appears if the report contains data items in the page layout that are not in a data container: - Nested List Report Containing a Data Item That is Grouped More Than Once Does Not Run After Upgrade
When you upgrade a nested list report that contains a data item that is grouped in both lists, the report does not run. - Background Color in Template Does not Appear
When creating a Query Studio template in Report Studio, if you add a list object and change its background color, the color change does not appear when you apply the template to a Query Studio report. - Subtotals in Grouped Lists
When using an IBM® Cognos® PowerCube that contains a ragged hierarchy, if you group on the first level in the hierarchy, subtotals may appear in the wrong place or show wrong values. - Chart Labels Overwrite One Another
In Report Studio and Query Studio, if you define a chart and render it in HTML or PDF format using the default sizes, the axis labels of the chart may overwrite each other. - Chart Shows Only Every Second Label
You create a report that includes a chart. The Allow Skip option is set to false, but when you run the report, labels are skipped. - Chart Gradient Backgrounds Appear Gray in Internet Explorer
In Report Studio, you can define a custom palette for a chart that includes a gradient. When the chart is rendered in HTML format in Microsoft Internet Explorer, the chart background appears gray. This is an Internet Explorer issue. - Metadata Change in Oracle Essbase Not Reflected in Reports and in the Studios
When there is a metadata change on the Oracle Essbase server, the change is not immediately reflected in the metadata tree in the studios. In addition, when a report is run, the report does not pick up the republished changes. - Relationships Not Maintained in a Report With Overlapping Set Levels
In a report, the relationship between nested or parallel member sets at overlapping levels in the same dimension may not always be maintained. - Summaries in Query Calculations Include Nulls with SAP BW Data Sources
When using an SAP BW data source in IBM Cognos Report Studio, null values in the database are returned in the result set and the count summary function includes the empty cells in the following scenarios: - Creating Sections on Reports That Access SAP BW Data Sources
SAP BW data sources may have problems with sections in reports under different circumstances: - Error Characters (--) Appear in Reports
When you run a report, you see two dash (--) characters in your report instead of values. - Columns, Rows, or Data Disappear With SSAS 2005 Cubes
Microsoft SQL Server 2005 Analysis Services (SSAS) has a feature called AutoExists that removes tuples that have no facts at the intersection of two hierarchies of the same dimension. - Function Unreliable with Sets
If you create an expression that uses the descendants function with sets, you may encounter unpredictable results. Some expected members may be missing or may have blank captions or labels. - Searching for values might return unexpected results
In the expression editor, when searching for values for a data item, the results you obtain might contain unexpected results if the data item is not a string data type. Because you can edit the expression for a data item, IBM Cognos Business Intelligence cannot determine with certainty what the data type is. - Report Differences Between TM1 Executive Viewer and IBM Cognos Business Intelligence with TM1 Data Sources
When using an IBM Cognos TM1® data source, comparable reports created in an IBM Cognos Business Intelligence studio and in TM1 Executive Viewer may contain different cell values. This occurs because the TM1 Executive Viewer product uses an algorithm for selecting default members for non-projected dimensions that differs slightly from traditional OLAP clients. - Order of Metadata Tree Differs for TM1 Data Sources
When using a an IBM Cognos TM1 data source, the order of members in the metadata tree of the Source tab of an IBM Cognos Business Intelligence studio may differ from the order shown in TM1 Architect. - MSR-PD-0012 error when importing external data
When you try to import an external data file, you receive an MSR-PD-0012 error. - MSR-PD-0013 error when importing external data
When you try to import an external data file, you receive an MSR-PD-0013 error.
Parent topic: Troubleshooting