This section contains additions and corrections that will appear in the next version of the Report Studio Professional Authoring User Guide.
Note: This topic will be added to the Troubleshooting appendix in the Report Studio Professional Authoring User Guide and the Administration and Security Guide in a future release.
When you upgrade a nested list report that contains a data item that is grouped in both lists, the report does not run and an error such as the following appears:
OP-ERR-0199: The query is not supported. The dimensions on the edge are inconsistent. The dataItems from dimension="[Product line]" must be adjacent.
This error occurs when the report is run against a dimensional data source and both lists are using the same query. This error does not occur if the report is run against a relational data source.
For example, you have a list that contains the grouped items Product line and Product type and a nested list that contains the data items Year, Quarter, and Unit sale price. Year, Quarter, and Product line are grouped items in the nested list.
To resolve the issue, delete the data item that is grouped in both lists from the inner list.
Click anywhere in the report.
In the Properties pane, click the select ancestor button and click the List link that represents the inner list.
Double-click the Grouping & Sorting property.
In the Groups pane, select the data item that you want and click the delete button.
Note: This topic will be added to the Report Studio Professional Authoring User Guide, the Report Studio Express Authoring User Guide, and the Query Studio User Guide in a future release.
When working with dimensional data sources, grouping by attributes is not supported. If you group by an attribute, the corresponding member is grouped instead, and there may be duplicate rows. For example, a list report contains the columns Color and Product Code, where Color is an attribute of Product Code. When you run the report, some colors, such as black, appear multiple times because several products are available in black. Each product is available in only one color, so the list has only one row for each product. Grouping the Color column does not change the output because the grouping is done on the Product Code column, and there is only one row for each product in the list. If the Product Code column is deleted, the output shows duplicate rows for some colors, such as black.
Note: This topic will be added to the Report Studio Professional Authoring User Guide, Report Studio Express Authoring User Guide, and the Query Studio User Guide in a future release.
There are limitations when aggregating DMR measures, semi-additive measures, and relational facts in crosstabs using the aggregation function count distinct, median, standard-deviation, or variance. The following limitations can cause error cells when the report is run:
The aggregation function must apply to all members of a level or all children of a member.
You cannot use certain OLAP functions in detail filters that are applied to a dimension that is not in the report or is at a level below what is being reported.
The supported OLAP functions are children, level, members, roleValue, and rootMembers.
You cannot define detail filters that reference one or more measures and are set to After auto aggregation.
You cannot define slicers that have more than one member from a dimension that does not appear in the report.
Slicers that have more than one member from a dimension that appears in the report produce errors in all cells that are ancestors of the slicer members.
If a crosstab has a row that is a set of members from one dimension (dimension A) and another row that is a set of members from another dimension (dimension B), and a slicer containing members from dimension A is defined, error cells are produced in the row that contains members from dimension B.
If a slicer is composed of members from a dimension, and a crosstab has a row that is a set of members from a higher level than the slicer members, error cells are produced for that row.
Error cells are produced when drilling down on a crosstab that has two nested levels.
If any of these limitations are not taken into consideration in a calculation, the report will not run. If there is a non-measure calculation that returns a constant or contains a summary function, and the calculation has a lower solve order than the measure being aggregated, error cells are returned for the aggregated measure.
In list reports, error cells are produced as a result of these limitations if the list uses an OLAP function other than children, filter, level, members, roleValue, and rootMembers.