![]() |
VOOZH | about |
Domo helps you manage, analyze, and share data across your entire organization, enabling decision makers to identify and act on strategic opportunities. Domo Workbench provides a secure, client-side solution for uploading your on-premise data to Domo. The CData ODBC Driver for SharePoint links Domo Workbench to operational SharePoint data. You can build datasets from SharePoint data using standard SQL queries in Workbench and then create real-time visualizations of SharePoint data in the Domo service.
The CData ODBC Drivers offer unmatched performance for interacting with live SharePoint data in Domo due to optimized data processing built into the driver. When you issue complex SQL queries from Domo to SharePoint, the driver pushes supported SQL operations, like filters and aggregations, directly to SharePoint 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 SharePoint data using native Domo data types.
Accessing and integrating live data from SharePoint has never been easier with CData. Customers rely on CData connectivity to:
Most customers rely on CData solutions to integrate SharePoint data into their database or data warehouse, while others integrate their SharePoint data with preferred data tools, like Power BI, Tableau, or Excel.
For more information on how customers are solving problems with CData's SharePoint solutions, refer to our blog: Drivers in Focus: Collaboration Tools.
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.
Set the URL property to the base SharePoint site or to a sub-site. This allows you to query any lists and other SharePoint entities defined for the site or sub-site.
The User and Password properties, under the Authentication section, must be set to valid SharePoint user credentials when using SharePoint On-Premise.
If you are connecting to SharePoint Online, set the SharePointEdition to SHAREPOINTONLINE along with the User and Password connection string properties. For more details on connecting to SharePoint Online, see the "Getting Started" 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.
After creating a DSN, you will need to create a dataset for SharePoint in Domo Workbench using the SharePoint DSN and build a visualization in the Domo service based on the dataset.
You can follow the steps below to build a dataset based on a table in SharePoint in Domo Workbench using the CData ODBC Driver for SharePoint.
SELECT * FROM MyCustomListNOTE: By connecting to SharePoint data using an ODBC driver, you simply need to know SQL in order to get your data, circumventing the need to know SharePoint-specific APIs or protocols.
With the dataset job run, the dataset will be accessible from the Domo service, allowing you to build visualizations, reports, and more based on SharePoint data.
With the DataSet Job saved and run in Domo Workbench, we are ready to build visualizations of the SharePoint data in the Domo service.
With the CData ODBC Driver for SharePoint, you can build custom datasets based on SharePoint data using only SQL in Domo Workbench and then build and share visualizations and reports through the Domo service.
Download a free trial of the SharePoint ODBC Driver to get started:
Download NowLearn more:
π SharePoint IconThe SharePoint ODBC Driver is a powerful tool that allows you to connect with live data from SharePoint and SharePoint Online, directly from any applications that support ODBC connectivity.
Access SharePoint data like you would a database - read, write, and update SharePoint Lists, Contacts, Calendar, Links, Tasks, etc. through a standard ODBC Driver interface.