![]() |
VOOZH | about |
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 Cvent links your Power BI reports to operational Cvent data. You can monitor Cvent data through dashboards and ensure that your analysis reflects Cvent 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 Cvent 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 Cvent data in Power BI due to optimized data processing built into the driver. When you issue complex SQL queries from Power BI to Cvent, the driver pushes supported SQL operations, such as filters and aggregations, directly to Cvent 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 Cvent data using native Power BI data types.
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.
Before you can authenticate to Cvent, you must create a workspace and an OAuth application.
To create a workspace:
| event/attendees:read | event/attendees:write | event/contacts:read |
| event/contacts:write | event/custom-fields:read | event/custom-fields:write |
| event/events:read | event/events:write | event/sessions:delete |
| event/sessions:read | event/sessions:write | event/speakers:delete |
| event/speakers:read | event/speakers:write | budget/budget-items:read |
| budget/budget-items:write | exhibitor/exhibitors:read | exhibitor/exhibitors:write |
| survey/surveys:read | survey/surveys:write |
After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.
After creating an OAuth application, set the following connection properties to connect to Cvent:
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.
π Configuring a DSN (NetSuite is shown).After creating a DSN, follow the steps below to connect to the Cvent DSN from Power BI Desktop:
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 Cvent data with other data sources, pivot Cvent columns, and more. Power BI detects each column's data type from the Cvent 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 Cvent data. When you click Close and Apply, Power BI executes the data retrieval query.
Otherwise, click Load to pull the data into Power BI.
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:
You can share reports based on ODBC data sources with other Power BI users in your organization using a Power BI Report Server.
Download a free trial of the Cvent ODBC Driver to get started:
Download NowLearn more:
π Cvent IconThe Cvent ODBC Driver is a powerful tool that allows you to connect with live data from Cvent, directly from any applications that support ODBC connectivity.
Access Cvent data like you would a database - read, write, and update Cvent 0, etc. through a standard ODBC Driver interface.