Alteryx Designer Desktop Ideas

Problem:
In large Alteryx workflows, renaming a column using a Select tool (or similar) causes downstream tools like Formula, Filter, Join, Sort, etc., to break or throw errors if they reference the old column name.
This means every time a column is renamed, I have to manually go through every tool that used the old name and update it - which is tedious, time-consuming, and error-prone.

Proposed Enhancement:
Add a feature to automatically propagate field name changes across all tools in the workflow that reference the renamed field.

This could work similarly to how modern IDEs allow you to "rename variable" across an entire codebase, or how refactoring works in platforms like Tableau Prep or Power BI.

Benefits:

• Saves time when making structural changes to data schemas.

• Reduces human error caused by missing updates in some tools.

• Makes workflows more scalable and easier to maintain.

• Improves usability and development speed for all users, especially in large or collaborative workflows.

We have a feature to limit the number of records, and I thought why not have a column limit as well? 

Columns take up a lot of space and processing, the more columns we have the more it slows down. So if we can declare it at the start to import the first 20 columns always, it’ll ensure that any new or unwanted columns in Excel will be avoided. 

Hi

Currently the date time now input outputs data only in string format, it could be useful if there was an option to output the data in date or date time format.

Hello,

The Data source window allow severla kind of connections like quick connect, ODBC, etc. But the order is not the same and this is confusing :

Best regards,

Simon

In 24.1 the email tool was adjusted such that any error in the workflow prevents the email tool from sending any emails. Previously, if AMP was enabled, the email tool could still send emails even if the workflow contained an error, but this is no longer the case. There are many cases where this is not ideal, one example being:

In larger workflows, I have multiple data streams which, after a point, operate independently. Even if one stream errors, I would like emails to be sent from the other streams. I have tried nesting the email tool within multiple layers of macros, but if any of the parent or child workflows/macros contain an error, the email tool will not send any emails. 

I would like a checkbox option in the email tool or workflow configuration that will still allow emails to be sent if the workflow errors. Then, with the use of control containers, I will have full control over email distribution with errors. 

For the Output Tool it would be very beneficial to be able to pass a password in order to populate a password protected Excel spreadsheet. It appears there is a decent amount of interest based on the Community feedback pertaining to the subject.

Hello,

There are several dozens of data sources... maybe it would be useful to have a search in it?

Best regards,

Simon

When loading multiple sheets from and Excel with either the Input Data tool or the Dynamic Input Tool, I usually want a field to identify which Sheet the data came from. Currently I have to import the Full Path and then remove everything except the SheetName.

It would be great if there was an option to output she SheetName as a field.

Idea: “Create THEN Append” Output Mode for Files and Databases

When outputting data in Alteryx—whether to an Excel file or a database table—the standard practice is:

First run: Set the output tool to “Create New Sheet” or “Create New Table.”

Subsequent runs: Manually change the setting to “Append to Existing.”

This works fine, but it’s very easy to forget to switch from "Create" to "Append" after the first run—especially in iterative development or when building workflows for others.

Suggested Enhancement:
Add a new option to the Output Data tool called:
“Create THEN Append”

Behavior:

On the first run, it creates the file/sheet or table.

On future runs, it automatically switches to append mode without needing manual intervention.

Why This Matters:
Prevents data loss from accidentally overwriting files/tables.

Improves automation and reusability.

Makes workflows more reliable when shared with others.

Mirrors functionality found in many ETL tools that allow dynamic "upsert-like" behavior.

Applies To:
Excel outputs (new sheet creation vs. append)

Database outputs (new table vs. append to existing)

CSV or flat file outputs where structure remains consistent

hello,

version 2021.4 does not allow workflows to run if any of their input files are open.... would be great to have an option for the input tool that switches on/off the ability to read from open files. Some of my input files have frequent data changes and i tend to keep them open while testing/simulating results

Thank you,

abdou 

Hi all,

When preparing reports with formatting for my stakeholders. They want these sent straight to sharepoint and this can be achieved via onedrive shortcuts on a laptop. However when sending the workflow for full automation, the server's C drive is not setup with the appropriate shortcuts and it is not allowed  by our admin team.

So my request is to have the sharepoint output tool upgraded to push formatted files to sharepoint. 

Thank you!

Please improve the Excel XLSX output options in the Output tool, or create a new Excel Output tool, 
or enhance the Render tool to include an Excel output option, with no focus on margins, paper size, or paper orientation

The problem with the current Basic Table and Render tools are they are geared towards reporting, with a focus on page size and margins.
Many of us use Excel as simply a general output method, with no consideration for fitting the output on a printed page.

The new tool or Render enhancement would handle different formats/different schemas without the need for a batch macro, and would include the options below.

The only current option to export different schemas to different Sheets in one Excel file, without regard to paper formatting, is to use a batch macro and include the CReW macro Wait a Second, to allow Excel to properly shut down before a new Sheet is created, to avoid file-write-contention issues.

Including the Wait a Second macro increased the completion time for one of my workflows by 50%, as shown in the screehshots below.

I have a Powershell script that includes many of the formatting options below, but it would be a great help if a native Output or Reporting tool included these options:

Allow options below for specific selected Sheet names, or for All Sheets

AllColumns_MaxWidth: Maximum width for ALL columns in the spreadsheet. Default value = 50. This value can be changed for specific columns by using option Column_SetWidth.

Column_SetWidth: Set selected columns to an exact width. For the selected columns, this value will override the value in AllColumns_MaxWidth.

Column_Centered: Set selected columns to have text centered horizontally.

Column_WrapText: Set selected columns to Wrap text.

AllCells_WrapText: Checkbox: wrap text in every cell in the entire worksheet. Default value = False.

AllRows_AutoFit: Checkbox: to set the height for every row to autofit. Default value False.

Header_Format: checkbox for Bold, specify header cells background color, Border size: 1pt, 2pt, 3pt, and border color, Enable_Data_Filter: checkbox

Header_freeze_top_row: checkbox, or specify A2:B2 to freeze panes

Sheet_overflow: checkbox: if the number of Sheet rows exceeds Excel limit, automatically create the next sheet with "(2)" appended

Column_format_Currency: Set selected columns to Currency: currency format, with comma separators, and negative numbers colored red.

Column_format_TwoDecimals: Set selected columns to Two decimals: two decimals, with comma separators, and negative numbers colored red.
Note: If the same field name is used in Column_Currency and Column_TwoDecimals, the field will be formatted with two decimals, and not formatted as currency.

Column_format_ShortDate: Set selected columns to Short Date: the Excel default for Short Date is "MM/DD/YYYY".

File_suggest_read_only: checkbox: Set flag to display this message when a user opens the Excel file: "The author would like you to open 'Analytic List.xlsx' as read-only unless you need to make changes. Open as read-only?
vb code: xlWB.ReadOnlyRecommended = True

File_name_include_date_time: checkboxes to add file name Prefix or Suffix with creation Date and/or Time

========

Examples:

My only current option: use a batch macro, plus a Wait a Second macro, to write different formats/schemas to multiple Sheets in one Excel file:

Using the Wait a Second macro, to allow Excel to shut down before writing a new Sheet, to avoid write-contention issues, results in a workflow that runs 50% longer:

Hello all,

As of today, you can only (officially) connect to a postgresql through ODBC with the SIMBA driver
help page :
https://help.alteryx.com/current/en/designer/data-sources/postgresql.html#postgresql

You have to download the driver from your license page

However there is a perfectly fine official driver for postgresql here https://www.postgresql.org/ftp/odbc/releases/

I would like Alteryx to support it for several obvious reasons :
1/I don't want several drivers for the same database
2/the simba driver is not supported for last releases of postgresql
3/the simba driver is somehow less robust than the official driver
4/well... it's the official driver and this leads to unecessary between Alteryx admin/users and PG db admin.

Best regards,

Simon

Referencing the previous idea: Inputs/Output should have the option to read/write a compressed file (ZIP or GZIP)

This idea has been implemented for inputting .zip files. However, we still need to use the run command workaround for outputs. It's very common for many users to want to output their .csv, .xlsx, .pdf to a .zip. The functionality would also need to extend to Gallery.

See the following links for people that are looking for this type of functionality:

https://community.alteryx.com/t5/Alteryx-Server-Discussions/Download-Multiple-Outputs-from-the-Galle...

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Output-files-to-ZIP/td-p/163502

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Zip-files/td-p/151456

Feel free to merge this idea with the previous one for continuity.

For companies that have migrated to OneDrive/Teams for data storage, employees need to be able to dynamically input and output data within their workflows in order to schedule a workflow on Alteryx Server and avoid building batch MACROs.

With many organizations migrating to OneDrive, a Dynamic Input/Output tool for OneDrive and SharePoint is needed.

• The existing Directory and Dynamic Input tools only work with UNC path and cannot be leveraged for OneDrive or SharePoint.
• The existing OneDrive and SharePoint tools do not have a dynamic input or output component to them.
• Users have to build work arounds and custom MACROS for a common problem/challenge.
  • Some users have identified a work around for the dynamic input (See Community Post)
• Users have to map the OneDrive folders to their machine (and server if published to the Gallery)
  • This option generates a lot of maintenance, especially on Server, to free up space consumed by the local version when outputting the data.

The enhancement should have the following components:

OneDrive/SharePoint Directory Tool

• Ability to read either one folder with the option to include/exclude subfolders within OneDrive
• Ability to retrieve Creation Date
• Ability to retrieve Last Modified Date
• Ability to identify file type (e.g. .xlsx) 
• Ability to read Author
• Ability to read last modified by
• Ability to generate the specific web path for the files

OneDrive/SharePoint Dynamic Input Tool

• Receive the input from the OneDrive/SharePoint Directory Tool and retrieve the data.

Dynamic OneDrive/SharePoint Output Tool

• Dynamically write the output from the workflow to a specific directory individual files in the same location
• Dynamically write the output to multiple tabs on the same file within the directory.
• Dynamically write the output to a new folder within the directory

Hello all,

As of now, you have two very distinct kinds of connection :

-in memory alias

-in database alias

It happens than every single time I use a in-database alias I have to create the same for in memory since some operations cannot be realized in in-database (such as pre-sql or interface tools)

What does that mean for us :

-more complex settings operations/training/tests

-unefficient worflows that have to deal with two kinds of alias.

What I propose :
-a single "connection alias", that can be used either for in-db either for in-memory,

-one place to configure

-the in-db or in-memory being dependant on the tools you use

Best regards,

Simon

Hi everyone,

Add two additional features to a directory tool. Something like this:

Use cases:

1. Since it is not possible to use a folder browse on the Gallery, this could help a basic user create a list of possible folders to select from with the help of a drop-down

2. Directory analysis for cleaning purposes - currently, if you want to get a list of the folders with Alteryx, it takes forever for big file servers since Alteryx is mapping all the files

Both are achievable today through regex or a bat script.

Thank you,

Fernando Vizcaino

This is a QoL-request, and I love me some QoL-updates!

While I'm developing I often need the output of a workflow as input for the next phase of my development. For example: an API run returns job location, status, and authentication ids. I want to use these in a new workflow to start experimenting what'll work best. Because of the experimenting part, I always do this in a new workflow and not cache and continue in my main flow.

Writing a temporary output file always feels like unnescesary steps, and tbh I don't want to write a file for a step that'll be gone before it reaches production. Esp if there is sensitive information in it.

Thanks.

Hello all,

As specified in the title, this idea is to distinguish between Append Prefix/Suffix to File and to Table on the Output Data Tool.


For most files (csv...), the table name does not really exist. However, for at least Excel files, if you choose this option, the result will be one sheet by suffix and the only option to have one file by suffix will be to change entire file path.

Best regards,

Simon