Ready to get started?

Learn more about the CData ODBC Driver for Sugar or download a free trial:

Download Now

Connect to and Query Sugar CRM Data in QlikView over ODBC

Create data visualizations with Sugar CRM data in QlikView.

The CData ODBC drivers expand your ability to work with data from more than 170 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 Sugar CRM data using the CData ODBC driver and create data visualizations in QlikView.

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

Connect to Sugar CRM 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 SugarCRM user credentials. This will use the default OAuth token created to allow client logins. OAuthClientId and OAuthClientSecret are required if you do not wish to use the default OAuth token.

You can generate a new OAuth consumer key and consumer secret in Admin -> OAuth Keys. Set the OAuthClientId to the OAuth consumer key. Set the OAuthClientSecret to the consumer secret.

Additionally, specify the URL to the SugarCRM account.

Note that retrieving SugarCRM metadata can be expensive. It is advised that you store the metadata locally as described in the "Caching Metadata" chapter of the help documentation.

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 Sugar CRM 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 Name, AnnualRevenue FROM Accounts
  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 SugarCRM Sys) in the resulting dialog. A command like the following is generated: ODBC CONNECT TO [CData SugarCRM 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 Name, AnnualRevenue FROM Accounts;

    Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to Sugar CRM, 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 Sugar CRM, typed appropriately for QlikView, thanks to built-in dynamic metadata querying.
  7. When defining Dimensions, select Name in the First Dimension menu.
  8. When defining Expressions, click the summary function you want and select AnnualRevenue in the menu.
  9. Finish the wizard to generate the chart. The CData ODBC Driver for Sugar CRM connects to live Sugar CRM 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.