1 Use the Data Model Editor

This topic describes the components and features supported by the data model editor.

Topics:

• What Is a Data Model?

• Components of a Data Model

• Features of the Data Model Editor

• About the Data Source Options

• Process Overview for Creating a Data Model

• Launch the Data Model Editor

• Data Model Properties

• Manage Private Data Sources

XML Data Chunking

XML data chunking supports distributed processing.

XML data chunking is suitable for large and long-running reports. If the administrator selects the Enable Data Chunking runtime property at the instance level, you can enable XML data chunking for individual data models, reports, and scheduled jobs.

In a data model, if you click Chunking, select Enable Chunking, and then specify an attribute in the Split By field, the data model pre-processor uses the split key to split large amounts of XML data into several chunks of data of manageable size.

Before you enable XML data chunking, understand its limitations and recommended usage.

XML data chunking:

• Is best suited for listing reports using a table and with no cross-references.
• Supports sorting, grouping, aggregation, and cross-referencing operations only within the individual chunked output. The merged output doesn't support these data operations.
• Adds page numbers to the PDF pages of the merged output. In the report template, remove the page numbering element to avoid duplicate or overlapping page numbers in the PDF output.
• Supports running totals, and other functions only within the individual chunked output, and each is reset with each chunked output.
• Supports only RTF, XPT, and eText, and XSL templates.
• Supports only PDF, XLSX, and Text output formats.
• Doesn't support multiple output formats. If you select XML chunking for a scheduled job, multiple outputs aren't allowed.
• Isn't supported for online reports.

Manage Private Data Sources

Data model developers can create and manage private JDBC, OLAP, web service, and HTTP data source connections without having to depend on an Administrator user. However, Administrator users can still view, modify, and delete private data source connections, if needed.

Private data source connections are identified by the word (Private) appended to the end of the data source name. For example, if you create a private JDBC connection called My JDBC Connection, it's displayed as My JDBC Connection (Private) in the data source drop-down lists.

If your user has the Administrator role, you can only create public data sources, even if you create the data source from the Manage Private Data Sources page.

1. Launch the data model editor.
   • To create a new data model, from the header or from the Home page, click Create, and then click Data Model.
   • To edit a data model, select the data model in the Catalog, and open the data model in the data model editor.
2. From the data model editor toolbar, click Manage Private Data Sources.
3. Select the connection type tab, and click Add Data Source.

   If you are logged in as an Administrator, the dialog displays all the data source connections; however, you can only create or modify JDBC, OLAP, HTTP, and web service data sources from this dialog.

4. Enter the private connection name, and the connection information.
5. Click Test Connection. A confirmation is displayed.
6. Click Apply. The private data source connection is now available for use in your datasets.