Apply a count operation on a column based on a query in which an explicit join occurs.
This applies the count after the join.
Count rows in a report by using a layout calculation object 
or by counting the literal value 1.
When you upgrade IBM Cognos 8, some reports may look or behave differently after the upgrade. The upgrade does not account for the following issues.
If advanced report authors used undocumented and unsupported features such as Javascript that refer to IBM Cognos HTML objects, they may have to recreate the features to complete the upgrade of the report.
Data may appear in a different order after upgrading. If sort order is important, ensure that the report or model specifies a sort order before upgrading.
Layout errors are suppressed by default in ReportNet. IBM Cognos 8 does not suppress layout errors. Users may have to correct or remove report layout expressions that cause errors.
If you used the default format in ReportNet, upgraded reports will retain that format. However, new reports in IBM Cognos 8 will use the IBM Cognos 8 format. If you want a consistent style across all reports, you must edit the styles property in each report and select or deselect the Use 1.x report styles option.
If you edited the ReportNet style sheet (default_layout.css) or the IBM Cognos 8 stylesheet (globalreportstyles.css), reports will lose the formatting after upgrading. You must reapply the changes to the IBM Cognos 8 stylesheets and copy the stylesheets to the IBM Cognos 8 server and the Web server.
PDF rendering in IBM Cognos 8 behaves like HTML rendering. After upgrading, PDF reports may have different font size, column wrapping, or word wrapping. You may have to change each affected report or change the default font in the IBM Cognos 8 style sheet.
If you use assignments of different data types after THEN and ELSE in ReportNet, the reports will generate invalid coercion errors after upgrading. You may have to recast the variables or change the assignments in the affected reports.
In previous versions of IBM Cognos 8, you could specify the solve order for objects such as crosstab node members . Solve order is now specified for data items. When you upgrade a report, solve orders specified in the report are moved to data items. For more information about solve order, see Resolve Multiple Calculations for Crosstabs and Charts.
In ReportNet, if a chart is created with a user-specified minimum value and all data values are below the minimum value, the chart starts at the user-specified minimum value and contains no data.
In IBM Cognos 8, the same parameters result in a chart that ignores the user-specified minimum value and uses a range that includes all of the data values for the chart.
If you specified in ReportNet that the processing for a query should be Database Only, when you upgrade your report to IBM Cognos 8, some processing may now occur locally.
In IBM Cognos ReportNet 1.1, double counting could occur when applying Count or Count Distinct to a query item. This occurred primarily when querying multiple query subjects that were joined 1-to-N in the model if the counted item existed in the query subject on the 1 side of the join. The explanation is that Count or Count Distinct was applied after the join operation.
Count Distinct worked only when the item to which Count Distinct was applied was the column used in the join. In this case, the column to be counted could have identical values for the different values used in the join condition.
In IBM Cognos 8, improvements to the count functionality cannot be handled through an automatic upgrade. The new approach avoids double counting on the 1 side of a 1-to-N join. The explanation is that Count or Count Distinct is now applied before the join operation.
There is now a lesser need to use Count Distinct and, when used, it will be successful more often. Count Distinct is no longer required to overcome double counting. Instead, it can be used as intended to select distinct values that exist in a query subject.
When you want to count repeated occurrences of a value, we recommend that you do one of the following:
Apply a count operation on a column based on a query in which an explicit join occurs.
This applies the count after the join.
Count rows in a report by using a layout calculation object or by counting the literal value 1.
