Alteryx File Types (2024)

.yxmd (Workflow)

An Alteryx workflow (.yxmd) represents a repeatable workflow process and has a file extension of .yxmd. All of the inputs, outputs, and tool configurations are saved within a single Alteryx workflow so that you can open and run the workflow multiple times.

For more information about workflows, see Workflow Configuration and Build Workflows.

.yxwg (Workflow group)

A workflow group (.yxwg) represents multiple workflows that can be saved and opened as one file. You can only create workflow groups of existing, locally saved workflows.

For more information, see Workflow Management.

.yxmc (Macro)

A macro (.yxmc) is a workflow that has the flexibility to be run as a single tool within another workflow. By using the macro design settings, the developer can specify parameters so that an end user has options to configure the workflow from a single tool. Once the workflow type is set as a macro, the options that are available in the Workflow Properties window change.

See Macros for more information about the different types of macros.

.yxwz (Analytic App)

An Analytic App (.yxwz ) is created in Alteryx Designer by a developer for end users to run in the Alteryx Analytic App environment. The developer creates a workflow in Alteryx, specifies a series of parameters that will define the user environment, and updates the original design workflow with the end-user's specifications. Analytic Apps can be accessed from a web browser if saved to the Gallery, or via a server or desktop installation. By using the Analytic App design settings, the developer can specify parameters so that an end user has options to configure the workflow from a single tool.

See Analytic Apps for more information about authoring Analytic Apps.

.yxzp (Packaged Workflow)

A .yxzp file is a workflow package that includes an Alteryx workflow (.yxmd, .yxmc, or .yxwz) and all of its dependencies zipped into a single file. This file can be imported into Alteryx, ensuring that workflows can easily be distributed and shared between users. A workflow package is created when a workflow is exported or saved to a Gallery.

See Workflow Management for more information about packaging a workflow.

.yxi (Packaged Tool)

A .yxi file is a package that includes an Alteryx tool and all of its dependencies zipped into a single file. When this file is installed in Alteryx Designer, from an external source such as the Alteryx Public Gallery (gallery.alteryx.com), the tool is added to the tool palette in the category specified.

The .yxi file, and any supporting macros required for the tool to work, are installed in:

\Users\<username>\AppData\Roaming\Alteryx\Tools\

Administrators can optionally choose to install a .yxi tool for all users, in which case the tool is installed in:

\ProgramData\Alteryx\Tools

A .yxi file must be installed before a workflow containing that tool can be run.

.yxdb (Alteryx Database)

The Alteryx database format (.yxdb) is a file type that can hold data fields, values, and spatial objects . The .yxdb format is the most efficient file type for reading and writing in Alteryx because it has no size limit, is compressed for maximum speed, and includes additional metadata that references the source of the data and how the data was created. While there is no limit to the number of records or file size, there is a record size limit of 2GB in a 64-bit environment.

See Alteryx Database File Format for more information.

.cydb (Calgary Database)

The Calgary database (.cydb) is a data file that uses indexing methodology to quickly retrieve records. A database index is a data structure that improves the speed of data retrieval operations on a database table. Indexes can be created using one or more columns of a database table, providing the basis for both rapid random look ups and efficient access of ordered records. There is a 2^31 limit on the number of records in a Calgary database (approximately 2 Billion). It is designed for around 100-300 million records.

See Calgary Tools for more information.

.cyidx (Calgary Index)

The Calgary index (.cyidx) is a dependency file for a Calgary database (.cydb). When a .cydb is written, an index file is created for each field of the Calgary database. The index makes it possible to quickly retrieve records based on specific queries configured by the user.

See Calgary Indexes for more information on how Alteryx creates indexes specific to different data types.

.yxwv (App Values)

The Alteryx App Values file (*.yxwv) is an .xml file that contains values and syntax that updates an Analytic App. Some Analytic Apps can have a lot of configuration options and user may want to save their specifications to use over and over again. They can save those selections to a .yxwv file so they do not need to populate the Analytic App interface each time they run the Analytic App. You can save and open a .yxwv file from the Analytic App interface.

.yxwv files are not encrypted. Any passwords included in them will be stored as clear text.

See Analytic Apps for more information.

.yxft (Field Types)

The Alteryx Field Type File (.yxft) is a text file that describes the file configuration of field names and field types. Once saved, the .yxft can be loaded via the Select tool or any tool with an embedded select.

From the Options menu of any Select Tool, the Save/Load options will create or access a previously created .yxft file.

.bak (Backup copy of a workflow)

A backup file (.bak) is created as soon as a workflow is edited and saved. The .bak file will be the workflow in its state prior to the most recent save. The .bak file is created in the same directory as the edited workflow and carries the same name.

.pcxml (Composer file)

A .pcxml file contains a proprietary language used by Alteryx for reporting purposes. Alteryx can read and render a .pcxml file for reporting output, but users are not encouraged to use this file type. Instead, create report snippets using the Reporting Tools and save to a .yxdb file or a final presentation output format.

.log (Log files)

Log files are created when the Alteryx engine, or a core component of the Alteryx engine, throws a fatal error. The log file contains information about where or how the failure occurred. If you report a fatal error to technical support, you may be asked to retrieve the log file. Log files are written to the following directory:

C:\Users\username\AppData\Local\Alteryx\ErrorLogs\<application name>

Application name refers to the area of Alteryx that is throwing the error. For example: AlteryxEngine, AlteryxCass, SrcLib_Dllx64, etc.

The following error messages will produce log files:

• An Unhandled Exception Error occurred.
• You have found a bug. Replicate, then let us know. We shall fix it soon.