View Reports on Real-Time HubDB Data in Power BI Report Server

With built-in support for ODBC on Microsoft Windows, CData ODBC Drivers provide self-service integration with self-service analytics tools, such as Microsoft Power BI. The CData ODBC Driver for HubDB links your Power BI reports to operational HubDB data. You can monitor HubDB data through dashboards and ensure that your analysis reflects HubDB data in real time by scheduling refreshes or refreshing on demand. This article details how to use the ODBC driver to create real-time visualizations of HubDB data in Microsoft Power BI Desktop and then publish the visualizations to Power BI Report Server.

The CData ODBC Drivers offer unmatched performance for interacting with live HubDB data in Power BI due to optimized data processing built into the driver. When you issue complex SQL queries from Power BI to HubDB, the driver pushes supported SQL operations, such as filters and aggregations, directly to HubDB and uses the embedded SQL Engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze HubDB data using native Power BI data types.

Connect to HubDB as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC data source name (DSN). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs. To publish Power BI reports from Power BI Desktop to Power BI Report Server, you will need to install the ODBC Driver on both the client (desktop) and server machines, using the same name for the DSN on each machine.

There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

Using a Custom OAuth App

AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

Follow the steps below to register an application and obtain the OAuth client credentials:

1. Log into your HubSpot app developer account.
   • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
2. On the developer account home page, click the Apps tab.
3. Click Create app.
4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
   • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
   • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
6. Click Create App. HubSpot then generates the application, along with its associated credentials.
7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

8. Under Scopes, select any scopes you need for your application's intended functionality.

   A minimum of the following scopes is required to access tables:

   • hubdb
   • oauth
   • crm.objects.owners.read
9. Click Save changes.
10. Install the application into a production portal with access to the features that are required by the integration.
    • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
    • Navigate to the copied link in your browser. Select a standard account in which to install the application.
    • Click Connect app. You can close the resulting tab.

Using a Private App

To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

You can generate a private application token by following the steps below:

1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
2. In the left sidebar menu, navigate to Integrations > Private Apps.
3. Click Create private app.
4. On the Basic Info tab, configure the details of your application (name, logo, and description).
5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
7. After you are done configuring your application, click Create app in the top right.
8. Review the info about your application's access token, click Continue creating, and then Show token.
9. Click Copy to copy the private application token.

To connect, set PrivateAppToken to the private application token you retrieved.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

After creating a DSN, follow the steps below to connect to the HubDB DSN from Power BI Desktop:

1. Open Power BI Desktop and click Get Data -> ODBC. To start Power BI Desktop from PowerBI.com, click the download button and then click Power BI Desktop.
2. Select a System DSN in the menu (necessary to publish to a Power BI Report Server). If you know the SQL query you want to use to import, expand the Advanced Options node and enter the query in the SQL Statement box. 👁 Selecting a System DSN
   
3. Select tables in the Navigator dialog. 👁 The available tables. (NetSuite is shown.)
   

4. Click Edit to edit the query. The table you imported is displayed in the Query Editor. In the Query Editor, you can enrich your local copy of HubDB data with other data sources, pivot HubDB columns, and more. Power BI detects each column's data type from the HubDB metadata retrieved by the driver.

   Power BI records your modifications to the query in the Applied Steps section, adjusting the underlying data retrieval query that is executed to the remote HubDB data. When you click Close and Apply, Power BI executes the data retrieval query.

   Otherwise, click Load to pull the data into Power BI.

Create Data Visualizations

After pulling the data into Power BI, you can create data visualizations in the Report view by dragging fields from the Fields pane onto the canvas. Follow the steps below to create a pie chart:

1. Select the pie chart icon in the Visualizations pane.
2. Select a dimension in the Fields pane, for example, PartitionKey.
3. Select a measure in the Name in the Fields pane, for example, Name. You can modify the visualization and the data used with the following techniques:
   • Change sort options by clicking the ellipsis (...) button for the chart. Options to select the sort column and change the sort order are displayed.
   • Use both highlighting and filtering to focus on data. Filtering removes unfocused data from visualizations; highlighting dims unfocused data. Highlight fields by clicking them.
   • Apply filters at the page level, at the report level, or to a single visualization by dragging fields onto the Filters pane. To filter on the field's value, select one of the values that are displayed in the Filters pane.
   👁 A pie chart showing Entity_Name and Total from the NetSuite SalesOrder table.
   
4. Click Refresh to synchronize your report with any changes to the data and save your Power BI report to the client machine.

Upload HubDB Data Reports to Power BI Report Server

You can share reports based on ODBC data sources with other Power BI users in your organization using a Power BI Report Server.

1. Install and configure the ODBC Driver for HubDB on the report server (see the instructions above).
2. Log into the report server (typically found at http://MYSERVER/reports), click to upload a new report and select the report you just saved. 👁 Uploading the Power BI Report to Power BI Report Server using the Web Portal.
   
3. View the HubDB report from any machine with access to the Report Server. 👁 Viewing the published report from the Report Server.