Connect to and Query OData Services in QlikView over ODBC



Create data visualizations with OData services in QlikView.

The CData ODBC drivers expand your ability to work with data from more than 200 data sources. QlikView is a business discovery platform that provides self-service BI for all business users in an organization. This article outlines simple steps to connect to OData services using the CData ODBC driver and create data visualizations in QlikView.

The CData ODBC drivers offer unmatched performance for interacting with live OData services in QlikView due to optimized data processing built into the driver. When you issue complex SQL queries from QlikView to OData, the driver pushes supported SQL operations, like filters and aggregations, directly to OData and utilizes 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 OData services using native QlikView data types.

Connect to OData as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

The User and Password properties, under the Authentication section, must be set to valid OData user credentials. In addition, you will need to specify a URL to a valid OData server organization root or OData services file.

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.

Populate a Chart with OData Services

The steps below supply the results of an SQL query to a visualization in QlikView. In this article, you will create a bar chart with the query below:

SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId
  1. Click File -> Edit Script (or click the Edit Script button in the Toolbar).
  2. On the Data tab, select ODBC in the Database menu and click Connect.
  3. Select the DSN (CData OData Sys) in the resulting dialog. A command like the following is generated: ODBC CONNECT TO [CData OData Sys];
  4. Enter the SQL query directly into the script with the SQL command (or click Select to build the query in the SELECT statement wizard). SQL SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId;

    Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to OData, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.

  5. Close the script editor and reload the document to execute the script.
  6. Click Tools -> Quick Chart Wizard. In the wizard, select the chart type. This example uses a bar chart. When building the chart, you have access to the fields from OData, typed appropriately for QlikView, thanks to built-in dynamic metadata querying.
  7. When defining Dimensions, select OrderName in the First Dimension menu.
  8. When defining Expressions, click the summary function you want and select Freight in the menu.
  9. Finish the wizard to generate the chart. The CData ODBC Driver for OData connects to live OData services, so the chart can be refreshed to see real-time changes. Live connections are possible and effective, thanks to the high-performance data processing native to CData ODBC Drivers.

Ready to get started?

Download a free trial of the OData ODBC Driver to get started:

 Download Now

Learn more:

OData Icon OData ODBC Driver

The OData ODBC Driver is a powerful tool that allows you to connect with live OData Services, directly from any applications that support ODBC connectivity.

Access OData services like you would any standard database - read, write, and update etc. through a standard ODBC Driver interface.