Connector catalog#
This is the overview of every datasource connector Reportworq can connect to. Each is added and tested the same way, in Settings > Integrations > DATASOURCES; see Connect a data source. The tables below give the category, the authentication approach, and the traps that most often block a connection.
The connectors that need the most setup have their own detailed pages, with screenshots and the full field-by-field walkthrough. Use this catalog to find the connector you need, then follow its detailed page:
- Connect IBM Planning Analytics for TM1 and Planning Analytics (self-hosted, Cloud (IBM SoftLayer), and Cloud (MCSP)).
- Connect SQL, OLE DB, and ODBC for relational databases, SQLite, and the CData bridged sources.
This catalog covers datasource connectors only, the sources Reportworq reads data from. AI provider connections (OpenAI, Azure OpenAI, and the other model providers, with their API keys) are a separate integrations family; to configure one, see Connect an AI provider.
OLAP and planning sources#
| Connector | Category | Auth and notes |
|---|---|---|
| IBM Planning Analytics (TM1) | OLAP / planning | Self-hosted (Native, Windows Integrated, or CAM), Cloud (IBM SoftLayer), or Cloud (MCSP). Some setups require config from IBM (CAM namespace, gateway URL, Welcome Kit user). See Connect IBM Planning Analytics. |
| Power BI / SSAS (ADOMD) | OLAP (native ADOMD; DAX, MDX, DMV) | Password, OAuth service principal, or OAuth interactive. See the Adomd traps below. |
| Workday Adaptive Planning | Planning API | Basic credentials, Adaptive Token, or Workday OAuth (5 fields). Metadata cache defaults to 24h; use Refresh Metadata after a structure change. Timeout defaults to 600s. |
| Anaplan | Planning API | Endpoint, Host, Authentication Endpoint (defaults to auth.anaplan.com), Username, Password. Credentials must match those used for the Anaplan Excel add-in. |
| Vena | Planning API | Basic credentials against the Vena API. |
| Pigment | Planning API | Export API Key, Metadata API Key, and Application. See the Pigment traps below. |
| Oracle (EPM Cloud / Smart View) | EPM Cloud REST, Basic auth | Host (<env>-<id>.epm.<region>.oraclecloud.com), tenant-prefixed Username (<tenant>.<user>), Password. This is not a relational Oracle database, see the trap below. |
Relational databases#
| Connector | Category | Auth and notes |
|---|---|---|
| SQL Server | Relational | Server, database, credentials. See Connect SQL, OLE DB, and ODBC. |
| OLE DB | Relational (generic OLE DB provider) | Freeform connection string; keep credentials out of it with %USERNAME% and %PASSWORD%. |
| ODBC | Relational (generic ODBC driver) | Freeform connection string; 64-bit System DSN with the driver installed on the Reportworq server. |
| SQLite | Relational (file-backed) | Connection string is a file path, Data Source=<path>, resolved on the Reportworq server; LIMIT dialect. |
| Snowflake | Relational (pre-configured OLE DB) | Cloud data warehouse. Ships as a pre-configured OLE DB connector, not CData; queried through table or SQL mode. |
CData bridged sources#
CData builds drivers that make an API or SaaS system look like a relational database. Reportworq licenses and embeds them so that a system with no SQL surface of its own, Salesforce or HubSpot for example, can be queried with the same table-or-SQL experience as SQL Server. That is why these connectors behave like the relational ones and why their connection properties look like a database connection string.
Every CData source Reportworq ships is listed below. Each connector name links to CData's own ADO.NET documentation for that driver, which is the authoritative reference for its connection properties, supported tables, and authentication options. Reach for it whenever you need a property that is not on the Reportworq form. For the shared setup, see Connect CData sources.
| Connector | Category | Auth and notes |
|---|---|---|
| Salesforce | CData (API to relational) | Basic auth: User, Password, and a Security Token. The token is not in the form, reset it in Salesforce (Profile > Settings > Reset my Security Token); it is emailed and appended to the password. |
| Jira | CData | Standard CData connection properties. |
| NetSuite | CData | Standard CData connection; can import a saved search schema. |
| Databricks | CData | Standard CData connection. |
| SAP HANA | CData | Standard CData connection. |
| HubSpot | CData | Standard CData connection. |
| Smartsheet | CData | Standard CData connection. |
| Dynamics 365 | CData | Standard CData connection. |
| Excel | CData | An Excel workbook exposed as a tabular source. |
| Power BI XMLA | CData | AzureAD (user) or AzureServicePrincipal (unattended, OAuth grant type CLIENT); needs Workspace=<name>, an XMLA-exposed workspace, and an approved Azure app registration. Distinct from the native Adomd connector. |
| Azure Analysis Services | CData | Tabular; standard CData connection. |
One source customers sometimes look for here is not a CData tile: Snowflake ships as a pre-configured OLE DB connector, see the relational table above.
Per-connector traps#
- Oracle is EPM Cloud / Smart View, not a relational database. The Oracle connector reads Smart View report specs and re-queries the Oracle EPM Cloud REST API with Basic auth. It has no table or SQL surface. To reach a relational Oracle database, use ODBC, OLE DB, or a CData driver instead.
- Salesforce needs a Security Token. Basic auth alone is not enough. Reset the security token in Salesforce; it is emailed to you and appended to the password. The connection fails without it.
- Pigment API-Export URLs are hard-validated. An API-export model supplies a URL and payload, and the URL must begin with
https://pigment.app/api. Any other URL is rejected at save with an error. - Pigment block imports. Block imports cover four block types (Metric, Dimension List, Transaction List, Table), each needing its own data connection after import.
- Re-importing creates a duplicate, not an update. Re-importing an already-imported Pigment block, or re-selecting an already-imported relational table, creates an additional copy rather than updating the existing one. Edit the existing item in place to avoid silent model bloat.
- Adomd (Power BI / SSAS) has three separate connection traps. First, MFA-required accounts cannot use password mode; switch to a service principal. Second, an MDX query must return a flat, tabular result or it errors; use the MDX query type's crosstab render mode for matrix output. Third, XMLA is only exposed on Power BI Premium, PPU, or Fabric workspaces (not shared or Pro), with the XMLA endpoint set to Read or Read/Write, and for service principals the tenant-admin setting "Allow service principals to use Power BI APIs."
- Workday Adaptive metadata is cached. The dimensional-structure cache defaults to 24h freshness. If a source's structure changed, use Refresh Metadata before a run; save changes first.
Notes and limits#
- Only administrators can add or configure datasource connectors.
- Datasource names must be unique, and editing, disabling, or deleting a live datasource breaks every job and form that refreshes from it. See Connect a data source.
- Writeback (data collection) paths, where available, are gated on a writeback license.
Going deeper. To turn any of these connectors into curated, reusable data for report authors, see Data models.
Feedback on this page
Comments, questions, requests, or something missing or unclear? Email us - the page you are on is filled in for you.
Email feedback on this pageOr write to support@reportworq.com directly.