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

The CData ODBC driver for Claude Compliance enables access to live data from Claude Compliance under the ODBC standard, allowing you work with Claude Compliance data in a wide variety of BI, reporting, and ETL tools and directly, using familiar SQL queries. This article shows how to connect to Claude Compliance 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 Claude Compliance data in Alteryx Designer due to optimized data processing built into the driver. When you issue complex SQL queries from Alteryx Designer to Claude Compliance, the driver pushes supported SQL operations, like filters and aggregations, directly to Claude Compliance 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 Claude Compliance data using native Alteryx data field types.

Connect to Claude Compliance 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.
   
   

   The driver connects to Claude Compliance using a Compliance Access Key, the only supported authentication method. Set the following connection property:

   • APIKey: The Compliance Access Key you created.

   Creating a Compliance Access Key

   1. Enable the Compliance API for your organization.
   2. Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
   3. Select Create Key and assign only the scopes your integration needs:
      • read:compliance_activities for Activities and the typed activity views.
      • read:compliance_org_data for organizations, roles, groups, and settings.
      • read:compliance_user_data for users, chats, files, projects, and downloads.
      • delete:compliance_user_data for the explicit Delete stored procedures.
   4. Create the key and copy it when it appears. The key starts with sk-ant-api01- and is shown only once.

   Optionally, set OrganizationUUID to limit organization-scoped views (such as OrganizationUsers and ComplianceRoles) to a single linked organization. If it is left empty, those views default to the first available organization and do not include data from all linked organizations.

   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. Open Alteryx Designer and create a new workflow.
3. 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
   2. Set the DCM Mode to "DCM Optional" and SDK Access Mode to "Allow" or "AllowAll"
4. Drag and drop a new input data tool onto the workflow.

5. Click the drop down under Connect a File or Database and select the Data sources tab.

6. Navigate tot he end of the page and click on "ODBC" under "Generic connection"
7. Select the DSN (CData Claude Compliance Source) that you configured for use in Alteryx.

8. 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 Claude Compliance, 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.


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 Claude Compliance data you want .

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

Perform Self-Service Analytics on Claude Compliance Data

You are now ready to create a workflow to prepare, blend, and analyze Claude Compliance 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 a browse data tool to the workflow.

3. Click to run the workflow (CTRL+R).

4. Browse your cleansed Claude Compliance data in the results view.

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