Notas del lanzamiento de Designer 2026.2

Los usuarios con flujos de trabajo creados en Designer 2025.2 o versiones posteriores ahora pueden publicarlos en versiones anteriores de Server que sean compatibles.

Para obtener información importante (incluidas limitaciones potenciales) y actualizaciones continuas, ve a Compatibilidad de versiones entre Designer y Server.

We have updated the tool configuration UI in the Output Data tool, including an improved connection creation experience.

Additionally, you can now connect the Output Data tool to datasets that you have access to in your active Alteryx One workspace.

The output configuration panel also includes additional output actions: relational datasets support append, create, drop, and update, while file-based datasets support create and overwrite.

Hemos realizado una serie de mejoras de usabilidad en la experiencia de Guardar como > Alteryx One en Designer. Esto incluye agregar información sobre herramientas, banners de información y la opción de restablecer dependencias para flujos de trabajo empaquetados.

The Alteryx One app supports temporary and permanent offline scenarios. If you don't have an internet connection, you can still launch Designer from the Alteryx One app and activate Designer offline if needed. After activation, you can continue using Designer while offline. Available functionality is limited to the features that Designer supports in offline mode.

La ventana de Designer que se inicia desde la aplicación Alteryx One muestra el mismo nombre de espacio de trabajo que el espacio de trabajo seleccionado actualmente en la ventana de la aplicación Alteryx One.

Para cambiar el espacio de trabajo, ve a la aplicación Alteryx One. No puedes cambiar el espacio de trabajo en Designer.

Control containers now distinguish between recoverable errors and exceptions that indicate code defects. Recoverable errors continue to appear as informational messages or warnings, while code defects are reported as errors to help identify issues that require investigation.

Designer now uses the AMP engine as the default engine for all new workflows. New workflows no longer include an option to use the original engine by default.

Existing workflows retain their current engine setting, and you can configure them to use either engine. Once you save an existing workflow configured to use the AMP engine, you can't revert the change.

We've converted the Python tool to work natively with the AMP engine.

The AMP Engine now uses a dynamic disk allocation strategy for spill files instead of fixed 256 KB blocks. Disk space is allocated based on the size of the compressed data, which can reduce disk usage and I/O overhead when workflows process highly compressible data, such as repetitive values.

The Select Fields option, available for Parquet files, lets you specify a comma-separated list of fields to read. The Input Data and Dynamic Input tools read only the selected fields, which can reduce the amount of data your workflow processes.

This feature is currently available only in Designer. If you run the workflow on an earlier version of Server (2026.1 and earlier), you may notice differences in execution time because this optimization isn’t yet supported.

We've standardized DCM connector forms across major connectors to provide a more consistent configuration experience. This update introduces clearer technology and authentication names, streamlined forms with improved field organization and help text, and removes redundant options to simplify connector setup.

You can continue to read from and write to Microsoft Excel 97–2003 (XLS) files by specifying the file path directly.

Designer now supports both 32-bit and 64-bit Microsoft Access Database Engine (ACE) drivers and automatically uses the latest installed version, preferring the 64-bit driver.

These changes align with the planned removal of 32-bit driver support starting in 2026.3.

We've improved compatibility with the renamed Databricks ODBC Driver, replacing the legacy Simba Spark ODBC Driver. This update helps prevent connection and workflow issues when migrating from the legacy driver.

We've added a new MERGE / UPSERT write mode to the native BigQuery connector. You can now update existing records and insert new records in a single bulk write operation by defining match key columns. MERGE processing runs directly in BigQuery, simplifying incremental data-loading workflows and providing a more consistent experience across cloud data warehouse connectors.

The Input Data tool includes a new Use String for Date/Time Types option for MapInfo TAB (.TAB) files.

By default, Designer imports date and time fields as strings to preserve existing behavior. Clear this option to import date, time, and datetime fields as native Alteryx data types for immediate use in date calculations and sorting.

If you execute the workflow on an earlier version of Server (2026.1 and earlier), this setting will be ignored.

Versión: 2026.2.0.8