Skip to main content

What's New in Designer

2026.4

Version: 2026.4 (For upgrade considerations as well as fixed and known issues, go to Release Notes)

New Features: Designer

Modern View Is Now the Default for New Designer Installs

When you launch Designer for the first time after a fresh install, it opens in the Modern View. Designer saves that starting view, so it opens the same way on later launches.

If you already use Designer, nothing changes. Designer keeps the view saved in your settings, or opens in Classic if none is saved. Your own choice always takes priority. If you switch views, Designer remembers the one you picked. Changing workspaces doesn’t change your view.

Designer opens in Classic when the first launch also opens a file or recovers an autosaved workflow.

Important

A fresh install is one where Designer has no saved settings and no application close date for the current Windows user. This applies to brand-new Designer users or those installing Designer for the first time on a new machine.

Python Tool Updates

Improved Editing Controls

The Python tool configuration panel now has visible controls for common script edits.

  • Find and Replace: Opens the editor’s find experience from a visible control. The Ctrl+F shortcut still works.

  • Comment: Comments or uncomments the current line or every non-blank line in your selection. Indentation stays the same.

  • Copy: Copies the full contents of the editor or the current selection.

  • Import: Replaces the previous Overwrite Script/Notebook option.

Simplified Installation of AYX Package in Custom Environments

A wheel for the ayx package has been included in the DesignerBaseTools_vEnv. For instructions on how to add the ayx package to your custom environment, go to Python tool.

Improved Syntax for Error Messages

Python tool error messages now start with the error type and description (for example, SyntaxError: invalid syntax) and no longer include the temporary file path. The updated format appears in the console and in the tooltip when you hover over the error icon. This change applies to the AMP engine only.

Turn Off Automatic Column Detection in Text Input

The Text Input tool now has an option to turn off automatic column (field) detection. When it's off, the tool outputs the values you enter or paste as strings. It doesn't infer column types or shorten column sizes from your data. This option works with both the original engine and the AMP engine.

Use this option to:

  • Keep leading zeros in identifiers.

  • Keep large numbers that look like numeric values.

  • Keep date-like text as entered.

  • Get predictable output field types and sizes.

  • Skip the extra processing that automatic field detection requires.

Important

Automatic column detection stays on by default. Existing workflows keep their current behavior. The option is saved with the tool configuration.

Assume Role Authentication Change

The existing Assume Role authentication method for Amazon S3 is now displayed as Assume Role (Deprecated). This authentication method continues to function, and existing workflows are not affected. Alteryx is preparing a new DCM-backed AWS Assume Role implementation planned for a future release. No migration is required in 26.4.

Parameter Support for SQL Server

TrustServerCertificate is now supported for SQL Server DCM DSN-less connections. You can configure certificate validation using the True/False option under Advanced SSL Options.

Reference Base Maps Upgrade

Upgraded map files to utilize MapServer 8 technology. To assist with this transition, the Data Products Download Portal will host both legacy map files and the updated MapServer 8 files.

AMP Fully-Converted Tools

These tools are now converted for full AMP support:

  • Map Input

  • Poly-Split

For a list of tools supported with AMP, go to Tool Use with AMP.

Parquet File Format Updates

Decimal128 Type Support for Parquet

We’ve added native support for reading Parquet decimal128 fields. Parquet decimal fields keep their declared precision and scale when read. This includes files from third-party tools.

Important

Note that decimal fields read from Parquet may now have a different type and size than in earlier versions.

Faster Parquet Reads in the AMP Engine

The AMP engine now reads large Parquet files faster. Designer reads multiple parts of a file at the same time instead of one after another, which reduces the time your workflow spends loading data. This applies to Parquet files stored locally and in supported cloud locations.

  • No configuration is needed. Existing workflows that read Parquet files benefit automatically, where the file and environment allow it.

  • Your results are unchanged. Records, field names, data types, values, and record order are preserved.

  • You can still see read progress and cancel a workflow while a Parquet file is being read.

New Compression Options for Parquet Files

Designer now supports Zstandard (Zstd) and Gzip compression for Parquet files, which improves interoperability with other tools that read and write Parquet.

  • Read: The Input Data tool reads Parquet files compressed with Zstd, Snappy, Gzip, or no compression. Designer detects the compression from the file, so you don't need to select anything.

  • Write: The Output Data tool has a new Compression option for Parquet files. Choose Snappy, Zstandard, Gzip, or Uncompressed. Snappy is the default, so existing workflows keep writing Snappy files.

Compression choice applies to Parquet files saved to a local path. Parquet files written to cloud locations continue to use Snappy compression. Using different compression libraries can achieve either faster execution or smaller file size.

Zstd Compression for YXDB Files

When you save a YXDB file from a workflow that uses the AMP engine, you can now choose between Snappy and Zstd compression. Zstd can store your data more efficiently.

  • Snappy is still the default, so existing workflows keep saving YXDB files as they do today.

  • You don't need to choose a compression setting when you read a YXDB file. An AMP workflow that supports Zstd reads files saved with either option and preserves records, field values, and field types, including spatial data.

  • Existing YXDB files remain readable. You don't need to convert or recreate them.

Important

Zstd-compressed YXDB files require a version of Designer that supports this option (2026.4+). If you share files with people on earlier versions, use Snappy.

Read All Excel Fields as Strings (AMP Engine)

The Input Data tool now has an XLSX option that reads every column as V_WString with one fixed field size. Use it when you combine many Excel files, for example with a wildcard in the Input Data tool or a template in the Dynamic Input tool. Without this option, a file fails the schema check if the same column is detected as a different type or size than in the first file, such as a column of numbers in one file and a column with one "N/A" cell in the next. With the option on, the types and sizes always match.

  • The option is available only with the AMP engine.

  • It is off by default. Existing workflows are unchanged.

  • After you read the data, use a Select or Auto Field tool to set the field types you need.

  • The option doesn't fix differences in column names, column count, or column order between files.

Dependency Management Updates in the Save As Dialog

We've rebuilt the saving experience to make it easier to understand and manage workflow dependencies. The updated dialog provides clearer information about asset types and their dependencies, helping you make informed choices when saving workflows to Alteryx One app.

  • Manage dependencies directly in the new Dependencies section.

  • View clearer messages about asset types and their dependencies. Designer Workflow Package (.yxzp) remains the default asset type.

  • Import a local macro to Alteryx One app from the Dependencies section. The workflow reference updates to use the newly created Alteryx One macro.

  • Include an Alteryx One Alteryx One macro in a workflow package (.yxzp) as an independent copy.

  • View detected local flat-file dependencies in the Dependencies section when saving a workflow as a .yxmd file.

Run and Schedule .yxmd Workflows in Alteryx One App

You can now run Designer Workflow (.yxmd) assets in Alteryx One app using Workspace Execution, and add them to Schedules and Plans. Designer Workflow Package (.yxzp) remains the default asset type in the Save dialog.

A .yxmd workflow doesn’t include its dependencies, so make sure they’re available in Alteryx One app before you run or schedule it.

Convert OneDrive-synced Local Files to Connections when Saving to Alteryx One (Public Preview)

When you save a Designer Desktop workflow to Alteryx One, Designer can now find Input Data and Output Data tools that point to local files synced from OneDrive. It converts them to connection-based files, so the workflow can run and be scheduled on Alteryx One without manual rework.

This applies to:

  • New workflows.

  • Local workflows that you save to Alteryx One.

  • Alteryx One workflows to which you add a new local dependency.

This feature is off by default. To turn it on, go to User Settings > General and select Convert local cloud-synced file paths to cloud connections. This setting also turns on detection of cloud-synced files when you drag them onto the canvas. When the setting is off, Designer saves local file paths exactly as you enter them.

If a workflow has other local file dependencies that can’t be converted, Designer warns you. Those workflows can’t run on Alteryx One until you resolve the dependencies or save the workflow as a .yxzp package.

Improved Meta Info Management for Designer Macros in Alteryx One

Improved Meta Info management for Designer Macros stored in Alteryx One. When working with cloud-stored macros, asset descriptions and versions now automatically align with Alteryx One asset details, while unsupported metadata fields are cleanly disabled to ensure workflow consistency and prevent misconfiguration.