• isRepeatColumnHeaders - indicates whether the column headers should be placed in front of columns each time a row break occurs. The default value is true.
• isRepeatRowHeaders - indicates whether the row headers should be placed in front of rows each time a column break occurs. The default value is true.
• columnBreakOffset - when a column break occurs, indicates the amount of vertical space, measured in pixels, before the subsequent crosstab piece to be placed below the previous one on the same page. The default value is 10.
• runDirection - indicates whether the crosstab data should be filled from left to right (LTR) or from right to left (RTL). The default value is LTR.
• ignoreWidth - indicates whether the crosstab will stretch beyond the initial crosstab width limit and dont't generate column breaks, or will stop rendering columns within the crosstab width limit and continue with the remaining columns only after all rows have started rendering. The default value is false.

• bucketExpression - the expression to be evaluated in order to obtain data group items
• comparatorExpression - needed in the case the natural ordering of the values is not the best choice
• orderByExpression - indicates the value used to sort data

• name - the name identifying the row group; this attribute is required.
• width - the width in pixels of the row group header
• totalPosition - specifies the position of the row containing total values relative to the row group. Possible values are: Start, End, None. The default value is None.
• headerPosition - specifies the position of the row header content when multiple enclosing row groups are declared. Possible values are: Top, Middle, Bottom, Stretch. The default value is Top.

• <bucket>
• <crosstabRowHeader>
• <crosstabTotalRowHeader>

• name - the name identifying the column group; this attribute is required.
• height - the height in pixels of the column group header
• totalPosition - specifies the position of the column containing total values relative to the column group. Possible values are: Start, End, None. The default value is None.
• headerPosition - specifies the position of the column header content when multiple enclosing column groups are declared. Possible values are: Left, Center, Right, Stretch. The default value is Left.

• <bucket>
• <crosstabColumnHeader>
• <crosstabTotalColumnHeader>

• name - the name identifying the measure.
• class - specifies the measure object type.
• calculation - like for report variables, specifies one of the supported types of calculations, except System. The default value is Nothing.
• incrementerFactoryClass - the name of the incrementer factory class
• percentageOf - indicates if the calculation should be performed as percentage of some other total value (usually the crosstab grand total).
• percentageCalculatorClass - the name of a custom percentage calculator class.

1. The current value of a measure calculation is stored in a variable having the same name as the measure.
2. <Measure>_<Column Group>_ALL - yields the total for all the entries in the column group from the same row.
3. <Measure>_<Row Group>_ALL - yields the total for all the entries in the row group from the same column.
4. <Measure>_<Row Group>_<Column Group>_ALL - yields the combined total corresponding to all the entries in both row and column groups
5. ROW_COUNT - variable that counts the rows in a row group
6. COLUMN_COUNT - variable that counts the columns in a column group

<style name="RowStyle" isDefault="false" mode="Opaque">
  <conditionalStyle>
    <conditionExpression><![CDATA[new Boolean($V{ROW_COUNT}.intValue() % 2 == 0)]] ></conditionExpression>
    <style backcolor="#E0E0E0"/>
  </conditionalStyle>
</style>

<style name="ColumnStyle" isDefault="false" mode="Opaque">
  <conditionalStyle>
    <conditionExpression><![CDATA[new Boolean($V{COLUMN_COUNT}.intValue() % 2 == 0)]] ></conditionExpression>
    <style backcolor="#E0E0E0"/>
  </conditionalStyle>
</style>

• <crosstabHeaderCell> - this is the topmost left crosstab cell, where row headers and column headers meet.
• <crosstabCell> - these are the regular detail cells, with no rowTotalGroup or columnTotalGroup attribute declarations within their body. For these cells the width and height attributes are mandatory.
• <crosstabCell> - if at least the rowTotalGroup or columnTotalGroup declaration is present, this cell becomes a total cell. With a rowTotalGroup attribute, it will display a column total for that row group. With a columnTotalGroup attribute, it will display a row total for that column group.
• <whenNoDataCell> - if present, it specifies the content to be rendered instead, when the crosstab dataset has no data

1. OrdersReport
   
   This report template shows how to use the most common crosstab features in order to represent aggregate data related to a set of shipment orders.
   • The crosstab is placed in the report summary.
   • It works with the report main dataset.
   • It uses conditional styles based on the ROW_COUNT variable.
   • Because data are not presorted, the engine performs internally data sorting, taking into account the <orderByExpression> criteria.
   • It contains a single row group, bucketing the country names, and a single column group bucketing freight values.
   • Detail cells contain multiple textfields with complementary information.
   • Row and column headers are placed in the start position, and total rows and columns are placed on the last position in the crosstab.
   • The crosstab do not split.

2. LateOrdersReport
   
   The report uses settings already present in the OrdersReport template, but due to not enough available space on the page, the crosstab splits with a row break and continues on the next page. One can see that column headers are not repeated on the next page, because the isRepeatColumnHeaders is set to false.

3. ProductsReport
   
   
   • The crosstab is placed in the report detail section.
   • It works with the Customer_Quantity subdataset.
   • It uses settings already present in the OrdersReport template.
   • A <whenNoDataCell> crosstab cell is declared within. If no records present in the dataset, the No data is printed instead.

4. ShipmentsReport
   
   This is the most complex report sample.
   
   
   • The crosstab is placed in the report detail section.
   • It works with the Country_Orders subdataset.
   • It uses settings already present in the above report templates.
   • Depending on the available space the crosstab splits into multiple fragments, either by inserting column breaks, or row breaks.
   • Row headers are repeating when columns break. Column headers are not repeating.
   • The <crosstabHeaderCell> is present within the crosstab.
   • Multiple row groups and column groups are declared. One can see how outer row headers are enclosing inner headers, and outer header columns are enclosing the inner headers. Also is shown the outer header cells content's behavior, relative to the available space in the header cell.
   • Percentage calculations are performed in total cells.

1. Subdataset attributes:
   • name
   • scriptletClass
   • resourceBundle
   • whenResourceMissingType
2. Subdataset elements:
   • <property/>
   • <scriptlet/>
   • <parameter/>
   • <queryString/>
   • <field/>
   • <sortField/>
   • <variable/>
   • <filterExpression/>
   • <group/>

 <element name="datasetRun">
  <annotation>
   <documentation>Subdataset instantiation information for a chart/crosstab dataset.</documentation>
  </annotation>
  <complexType>
   <sequence>
    <element ref="jr:parametersMapExpression" minOccurs="0" maxOccurs="1"/>
    <element ref="jr:datasetParameter" minOccurs="0" maxOccurs="unbounded"/>
    <choice minOccurs="0" maxOccurs="1">
     <element ref="jr:connectionExpression"/>
     <element ref="jr:dataSourceExpression"/>
    </choice>
   </sequence>
   <attribute name="subDataset" type="string" use="required">
	<annotation>
 	 <documentation>The name of the <elem>subdataset</elem> to instantiate.</documentation>
	</annotation>
   </attribute>
  </complexType>
 </element>