VOOZH about

URL: https://www.cdata.com/kb/tech/xml-odbc-alteryx.rst

⇱ Prepare, Blend, and Analyze XML Data in Alteryx Designer (ODBC)


Prepare, Blend, and Analyze XML Data in Alteryx Designer (ODBC)

πŸ‘ Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Build workflows to access live XML data for self-service data analytics.

The CData ODBC driver for XML enables access to live data from XML under the ODBC standard, allowing you work with XML data in a wide variety of BI, reporting, and ETL tools and directly, using familiar SQL queries. This article shows how to connect to XML data using an ODBC connection in Alteryx Designer to perform self-service BI, data preparation, data blending, and advanced analytics.

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

Connect to XML Data

  1. If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can configure the DSN using the built-in Microsoft ODBC Data Source Administrator. This is also the last step of the driver installation. See the "Getting Started" chapter in the Help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

    Connecting to Local or Cloud-Stored (Box, Google Drive, Amazon S3, SharePoint) XML Files

    CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.

    Setting connection properties for local files

    Set the URI property to local folder path.

    Setting connection properties for files stored in Amazon S3

    To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:

    • AWSAccessKey: AWS Access Key (username)
    • AWSSecretKey: AWS Secret Key

    Setting connection properties for files stored in Box

    To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.

    Dropbox

    To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.

    SharePoint Online (SOAP)

    To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.

    SharePoint Online REST

    To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.

    Google Drive

    To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.

    The property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

    • Document (default): Model a top-level, document view of your XML data. The data provider returns nested elements as aggregates of data.
    • FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
    • Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

    See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

    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.

  2. πŸ‘ Configuring the DSN (Salesforce is shown.)
  3. Open Alteryx Designer and create a new workflow.
  4. If your application is set to run in DCM Mode Only by default, you need to change it to DCM Mode Optional to enable the CData ODBC Driver connection:
    1. Open Options > User Settings > Edit User Settings πŸ‘ Opening User Settings
    2. Set the DCM Mode to "DCM Optional" and SDK Access Mode to "Allow" or "AllowAll" πŸ‘ Overriding DCM Settings
  5. Drag and drop a new input data tool onto the workflow.
  6. πŸ‘ Add a new Input Data tool to the Workflow.
  7. Click the drop down under Connect a File or Database and select the Data sources tab.
  8. πŸ‘ Navigate to the Data sources tab.
  9. Navigate tot he end of the page and click on "ODBC" under "Generic connection" πŸ‘ Select New ODBC Connection.
  10. Select the DSN (CData XML Source) that you configured for use in Alteryx.
  11. πŸ‘ Select the configured DSN.
  12. In the wizard that opens, drag, and drop the table to be queried in the "Query Builder box." Select the fields by checking the boxes that you wish to include in your query. Where possible, the complex queries generated by the filters and aggregations will be pushed down to XML, 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 connector.
  13. πŸ‘ Select table(s) and field(s) (Salesforce is shown).

    If you wish to further customize your dataset, you can open the SQL Editor and modify the query manually, adding clauses, aggregations, and other operations to ensure that you are retrieving exactly the XML data you want .

    πŸ‘ Modify the query in the SQL Editor.

With the query defined, you are ready to work with XML data in Alteryx Designer.

πŸ‘ The configured Data Input tool, complete with query.

Perform Self-Service Analytics on XML Data

You are now ready to create a workflow to prepare, blend, and analyze XML data. The CData ODBC Driver performs dynamic metadata discovery, presenting data using Alteryx data field types and allowing you to leverage the Designer's tools to manipulate data as needed and build meaningful datasets. In the example below, you will cleanse and browse data.

  1. Add a data cleansing tool to the workflow and check the boxes in Replace Nulls to replace null text fields with blanks and replace null numeric fields with 0. You can also check the box in Remove Unwanted Characters to remove leading and trailing whitespace.
  2. πŸ‘ Add and configure a new Data Cleansing tool.
  3. Add a browse data tool to the workflow.
  4. πŸ‘ Add a new Data Browse tool.
  5. Click to run the workflow (CTRL+R).
  6. πŸ‘ Run the workflow.
  7. Browse your cleansed XML data in the results view.
  8. πŸ‘ Browse the results of the Workflow (Salesforce is shown.)

Thanks to built-in, high-performance data processing, you will be able to quickly cleanse, transform, and/or analyze your XML data with Alteryx.

Ready to get started?

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

 Download Now

Learn more:

πŸ‘ XML Documents Icon
XML ODBC Driver

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

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