View Reports on Real-Time Harvest 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 Harvest links your Power BI reports to operational Harvest data. You can monitor Harvest data through dashboards and ensure that your analysis reflects Harvest 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 Harvest 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 Harvest data in Power BI due to optimized data processing built into the driver. When you issue complex SQL queries from Power BI to Harvest, the driver pushes supported SQL operations, such as filters and aggregations, directly to Harvest 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 Harvest data using native Power BI data types.

Connect to Harvest 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.

Start by setting the Profile connection property to the location of the Harvest Profile on disk (e.g. C:\profiles\Harvest.apip). Next, set the ProfileSettings connection property to the connection string for Harvest (see below).

Harvest API Profile Settings

To authenticate to Harvest, you can use either Token authentication or the OAuth standard. Use Basic authentication to connect to your own data. Use OAuth to allow other users to connect to their data.

Using Token Authentication

To use Token Authentication, set the APIKey to your Harvest Personal Access Token in the ProfileSettings connection property. In addition to APIKey, set your AccountId in ProfileSettings to connect.

Using OAuth Authentication

First, register an OAuth2 application with Harvest. The application can be created from the "Developers" section of Harvest ID.

After setting the following connection properties, you are ready to connect:

• ProfileSettings: Set your AccountId in ProfileSettings.
• AuthScheme: Set this to OAuth.
• OAuthClientId: Set this to the client ID that you specified in your app settings.
• OAuthClientSecret: Set this to the client secret that you specified in your app settings.
• CallbackURL: Set this to the Redirect URI that you specified in your app settings.
• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage how the driver obtains and refreshes the OAuthAccessToken.

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 Harvest 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.
3. Select tables in the Navigator dialog.

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 Harvest data with other data sources, pivot Harvest columns, and more. Power BI detects each column's data type from the Harvest 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 Harvest 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, Id.
3. Select a measure in the ClientName in the Fields pane, for example, ClientName. 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.
4. Click Refresh to synchronize your report with any changes to the data and save your Power BI report to the client machine.

Upload Harvest 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 Harvest 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.
3. View the Harvest report from any machine with access to the Report Server.