Supported Tools for Column-Level Lineage
This article describes the tools and connection types that currently support column-level lineage. For information about how to configure and establish a connection between Alteryx One Platform and Alteryx Server, see the Data Lineage Connection help page.
Supported Tools
Nota
All Documentation and Interface tools do not affect data lineage. These tools are therefore considered de facto supported for lineage purposes.
The Browse tool also does not generate lineage information.
We support these Alteryx tools:
Tool Category | Tool Name |
|---|---|
Developer | Block Until Done |
Developer | Control Container |
Developer | Dynamic Input |
Developer | Dynamic Rename |
Developer | Run Command |
In/Out | Input Data |
In/Out | Output Data |
Join | Append Fields |
Join | Join |
Join | Union |
Parse | DateTime |
Parse | Text To Columns |
Preparation | Data Cleanse Pro |
Preparation | Filter |
Preparation | Formula |
Preparation | Multi-Row Formula |
Preparation | Record ID |
Preparation | Sample Note: The Sample tool won’t support the “1 in N chance to include each row” mode. |
Preparation | Select |
Preparation | Sort |
Preparation | Unique |
Transform | Count Records |
Transform | Cross Tab |
Transform | Summarize |
Transform | Transpose |
Supported Connection Types
We support these connection types:
Nota
We don’t currently support Custom SQL Queries as an input, but we plan to add support in a future version.
Connection Type | Underlying Provider | OL Namespace Examples1 |
|---|---|---|
MicrosoftExcel(*.xlsx) | File | |
Comma-DelimitedTextFiles(.csv) | ||
MicrosoftExcelMacroEnabled (.xlsm) | ||
TableauHyperDataExtract (.hyper) | ||
ODBCDatabase(odbc:) | SQL Server | |
Azure SQL Server | ||
Oracle | | |
Snowflake | | |
Amazon Redshift | | |
PostgresSQL | | |
Teradata | | |
SAPHana | | |
MySQL | | |
IBM DB2 | | |
Spark | | |
Databricks | | |
Google BigQuery | | |
OracleDatabase(oci:) | Oracle | |
SQLServerBulkLoader(ssvb:) | SQLServer | |
SnowflakeBulkLoader(snowbl:) | Snowflake | |
AmazonRedshiftBulkLoader (rsbl:) | Redshift | |
1For namespaces in the format {host}:{port}, the host can be specified as a DNS name or an IP address. The port is optional.
Unsupported Tools and Connection Types
If a workflow includes an unsupported tool, Alteryx can still detect and display that the component is part of the process. However, column-level lineage mapping is not generated for that tool.
If a workflow includes an unsupported connection type, Alteryx cannot send any lineage information for that input. This applies to both dataset-level and column-level lineage.
You will still see the columns used as inputs and produced as outputs.
You will not see column-to-column relationships for any transformations or data movement through the unsupported tools or connections. In the lineage view or in your data catalog, these columns appear as unmapped.
This behavior helps preserve lineage integrity. If any tool or connection type between input and output nodes isn’t supported, Alteryx can’t fully trace the data flow through that step. To maintain accuracy, no partial or inferred mappings are created.
In summary:
Supported tools and connection types: Full column-level mapping is captured.
Inputs and outputs are partially visible.
Unsupported tools and connection types: No lineage is captured.