Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Connect to and Query Printify Data in QlikView over ODBC
Create data visualizations with Printify data 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 Printify data using the CData ODBC driver and create data visualizations in QlikView.
The CData ODBC drivers offer unmatched performance for interacting with live Printify data in QlikView due to optimized data processing built into the driver. When you issue complex SQL queries from QlikView to Printify, the driver pushes supported SQL operations, like filters and aggregations, directly to Printify 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 Printify data using native QlikView data types.
Connect to Printify 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.
Start by setting the Profile connection property to the location of the Printify Profile on disk (e.g. C:\profiles\Profile.apip). Next, set the ProfileSettings connection property to the connection string for Printify (see below).
Printify API Profile Settings
In order to authenticate to Printify, you'll need to provide your API Key. To get your API Key navigate to My Profile, then Connections. In the Connections section you will be able to generate your Personal Access Token (API Key) and set your Token Access Scopes. Personal Access Tokens are valid for one year. An expired Personal Access Token can be re-generated using the same steps after it expires. Set the API Key to your Personal Access Token in the ProfileSettings property to connect.
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 Printify Data
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 Id, ShippingMethod FROM Tags WHERE Status = 'pending'
- Click File -> Edit Script (or click the Edit Script button in the Toolbar).
- On the Data tab, select ODBC in the Database menu and click Connect.
- Select the DSN (CData API Sys) in the resulting dialog.
A command like the following is generated:
ODBC CONNECT TO [CData API Sys];
- 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 Id, ShippingMethod FROM Tags WHERE Status = 'pending';
Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to Printify, 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.
- Close the script editor and reload the document to execute the script.
- 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 Printify, typed appropriately for QlikView, thanks to built-in dynamic metadata querying.
- When defining Dimensions, select Id in the First Dimension menu.
- When defining Expressions, click the summary function you want and select ShippingMethod in the menu.
Finish the wizard to generate the chart. The CData ODBC Driver for Printify connects to live Printify data, 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.