The CData JDBC Driver for Anaplan represents Anaplan data as a relational database, making it easy to query using standard SQL.

It maps Anaplan concepts to a familiar database hierarchy:

• Workspaces are represented as catalogs.
• Models within a workspace are represented as schemas.
• Export actions defined in Anaplan are represented as tables within their corresponding model schema.

Note: Export actions must be created in Anaplan (in CSV format) before they can be queried. The driver retrieves data by executing these exports and returning the results.

The data model is organized into two main parts:

• A generic Information schema that contains administrative and metadata entities.
  • The tables in this schema use the Transactional APIs, which do not support bulk/asynchronous data retrieval. For this reason, the effects of connection properties like Timeout and Pagesize apply to queries made in this schema, but those of BulkTimeout and BulkPageSize do not.
• A separate schema for each Model, containing data available within that model.

Modeling Export Layouts as Tables

The layout you select (in the Anaplan user interface) for an export action influences how the driver exposes the data from the export in tabular form.

For the most table-like data structure, use Tabular Single Column exports (recommended), where each row represents a single data point with normalized dimensions. The driver exposes such exports with the same rows and columns seen in the export.

If you query an export configured with a Grid or Tabular Multiple Column layout, the driver auto-assigns each column a sequential name (Col0, Col1, Col2, etc.) and treats all rows, including those containing hierarchical horizontal or vertical dimension labels, as data records.

Accessing Workspaces and Models

The workspaces and models visible to you depend on your Anaplan user role:

• Regular users only see workspaces and models to which they are explicitly assigned.
• Users with administrative permissions can see all workspaces and models in the tenant, but may not be able to query data within them without explicit access permissions.
• User administrators can see all workspaces and models, but the driver automatically filters to only those where you have entitlements or permissions, improving performance.

Note: You can use the Catalog and Schema connection properties to narrow the scope to a single workspace or model, which is recommended for better performance.