Connect CData sources#
Several connectors reach their source through a CData driver. CData drivers wrap an API or SaaS system and present it to Reportworq as a relational, tabular source, so you query it with the same table or SQL modes as any database. Reportworq uses CData so that systems with no native SQL interface, such as Salesforce or Jira, can still feed a data model and be refreshed on every job run.
Supported CData connectors#
Reportworq ships CData drivers for the sources below. Each name links to CData's own ADO.NET documentation for that driver, which is the authoritative reference for its connection properties, the tables it exposes, and the authentication options it supports. Go there whenever you need a property that is not on the Reportworq form.
| Source | Driver documentation |
|---|---|
| Azure Analysis Services | ADO.NET provider docs |
| Databricks | ADO.NET provider docs |
| Dynamics 365 | ADO.NET provider docs |
| Excel (a workbook exposed as a tabular source) | See Connect Excel, or the ADO.NET provider docs |
| HubSpot | ADO.NET provider docs |
| Jira | ADO.NET provider docs |
| NetSuite (can also import a saved-search schema) | ADO.NET provider docs |
| Power BI XMLA (the tile PowerBI XMLA - SQL, distinct from the native Power BI / SSAS ADOMD connector) | ADO.NET provider docs |
| QuickBooks Online | See Connect QuickBooks Online |
| SAP HANA | ADO.NET provider docs |
| Salesforce | ADO.NET provider docs |
| Smartsheet | ADO.NET provider docs |
| Workday (Financial Management and HCM, not Workday Adaptive Planning) | ADO.NET provider docs |
Snowflake is supported two ways: through the shipped CData SnowFlake driver and its guided field editor (the preferred method), or through a native ODBC connection using the generic ODBC Provider tile. Both are valid connection methods. See the dedicated Connect Snowflake page for the guided CData setup, and Connect Snowflake via ODBC for the ODBC alternative.
Configure a CData connection#
- Add the CData connector you need and open its editor.
- Provide the connection details. Most drivers accept a standard connection string of CData connection properties, and most also support OAuth for authentication. For an OAuth driver, complete the interactive Authenticate step, or supply the service-principal or client credentials the driver requires, so Reportworq can obtain and refresh a token.
- Where the driver exposes separate credential fields, enter secrets there rather than in the visible connection string.
- Save and select Test connection.
- Query the source in a data model through table or SQL mode, exactly as for the SQL connectors; see Query the source in a data model.
For per-connector traps, such as the Salesforce security token or the Power BI XMLA workspace and Azure app registration, see the Connector catalog. For QuickBooks Online, which signs in with OAuth, see Connect QuickBooks Online, including how to complete the sign-in on a headless or server install where there is no browser on the server. For Workday, see the Workday notes in the Connector catalog.
Find the connection properties for a driver#
Each CData driver has its own connection properties and authentication options. To find them, start from the CData drivers documentation, open the driver for your source, then open its ADO.NET online documentation, which lists the connection-string properties and the OAuth setup for that source.
Related pages#
- Connect SQL Server, OLE DB, and ODBC for the relational connectors the CData drivers are built on, including the shared query modes.
- Connect Snowflake and Connect Snowflake via ODBC.
- Connect QuickBooks Online.
- Connect Excel for a workbook on the server or inside the repository.
- Connector catalog for every connector Reportworq ships and its per-connector traps.
Going deeper. To curate columns into governed business fields, set filters, and publish a view 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.