Creating a report document
Generate a report document from a report design by choosing RunGenerate Document. Specify the folder in which to save the report document. To share the report document with other report developers, put the file in a shared resource folder.
When used as a data source, the report document provides access to its result sets. At report generation, a result set is created for each table, chart, cross tab, and list. The data in a result set is defined by the data column bindings created for a table, chart, cross tab, or list. A report design has access to all result sets in a report document, except for a cross tab’s result set.
For example, Figure 6-1 shows a report that displays sales data in two tables and a chart.
Figure 6-1  
A report design that uses a report document generated from this report has access to the result sets generated for the two tables and the chart. When you create a data set to specify which result set data to use, the data set editor displays all the available results sets, as shown in Figure 6-2.
Figure 6-2  
The result sets are organized under three categories: Bookmark, Element ID, and Result Set ID. The result sets named __bookmark_1, __bookmark_2, and __bookmark_3 correspond to the result sets for the first table, the chart, and the second table, respectively. Similarly, the result sets named Table_252, Chart_312, and Table_6 correspond to the result sets for the first table, the chart, and the second table. Finally, the result sets named QuRs0, QuRs1, and QuRs2 also correspond to the result sets for the first table, the chart, and the second table.
While it seems redundant to provide three methods to select any given result set, each method offers different benefits.
For result sets that appear under Bookmark, the report developer designing the report from which a report document is generated can specify descriptive names. The name can be a literal string or an expression.
For results sets that appear under Element ID, the report developer can also specify descriptive names, but can only use literal strings to do so. Result sets are also organized hierarchically if a report, such as a master-detail report, contains nested tables.
For result sets that appear under Result Set ID, the report developer cannot specify alternate names. These generated names are useful for accessing a result set programmatically.
Figure 6-3 shows another example of the data set wizard displaying the result sets available to a report design.
Figure 6-3  
This time, the result sets under Bookmark use custom names, rather than the default __Bookmark_#. Result sets under Element ID are organized hierarchically under Orders and Payments, which are custom names. This hierarchy reflects the structure of data in the report document.

Additional Links:

Copyright Actuate Corporation 2012