Alteryx Designer Desktop Ideas

Issue

Whenever a Summarize tool is used, it renames the output field (e.g., sales becomes SUM_sales or AVG_sales).  

Proposal

I think a reasonable compromise is to by default not rename fields in the Summarize Tool, but to include an option (in the tool, or in global settings) to allow for renaming.

Rationale

I have yet to come across a use case where automatic renaming of aggregated fields is desirable. What I have come across is the annoyance to rename the fields back to what they were with a Dynamic Rename tool, and sometimes having to do this multiple times (e.g., converting back a SUM_SUM_SUM_sales back to sales). Additionally, automatic field renaming causes workflow errors when workflows are later modified by adding/removing a Summarize tool (e.g., if you later add a Summarize tool, all downstream steps will expect the "sales" field and not know to use the "Sum_sales field). 

Automatic Renaming feels very much like historic Excel with Pivot Tables field renaming and not reflective of modern code-based workflow best practices.

I appreciate you considering this improvement.

The current update notification in Alteryx Designer can feel overly persistent and disruptive — especially for enterprise users whose Designer must stay compatible with an Alteryx Server version. Users often see repeated prompts to upgrade Designer to the newest version, even when doing so would break compatibility with their organization’s Server, which can cause errors, confusion, or rework.

Proposed Solution:

Server Version Awareness:
When Designer is connected to Alteryx Server, automatically check the Server version and suppress any upgrade prompt that would lead to a version mismatch.

Flexible Dismissal:
Allow users to snooze or permanently dismiss the update notification for the current version cycle - or dismisal longer than 30 days which is the current max - rather than re-seeing the prompt each launch.

Impact:

Prevents accidental incompatibility between Designer and Server

Reduces user frustration with repetitive prompts

Why This Matters:

Many organizations cannot upgrade Designer independently of Server, and compatibility mismatches lead to support tickets and lost productivity. A smarter, quieter update experience respects these realities and makes version management more reliable for everyone.

Hello all,

A few years ago, I asked for svg support in Alteryx (https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/svg-support-for-icon-comment-image-e... ). Now, there is Alteryx Designer Cloud with other icons... already in svg !




So I think it would be great to have an harmonization between designer and cloud.

Best regards,

Simon

If the tables in the config window has lots of rows, it is quite complicated to find those of interest. 

Please add a filter or search option (e.g. by the field name) to display only the relevant rows.

It would also be helpful to select or deselect multiple selected rows with one click.

Find an example from the "Select-Tool":

To increase Performance on some old Buissness Logic, i am trying to switch an existing system to In-DB tools. This has given me a lot of headache because there is no Multi-Field Formular Tool in the In-DB section. It is a very tedious job to run through every workflow to manually set the same regex for a table with more than 20 Fields. 

I have had the idea to implement such a tool myself but i think this could be helpful for other developers in Alteryx Desktop too, so i am bringing this up here.

The Idea is to have a similar approach to the new Multi-Formular Tool like the other already existing Tool in Preperation. 

I would like to see Designer offer me the ability to chain workflows together where once Workflow A completes, Workflow B will automatically start.  There are times when linear processing is required in order to avoid dependency issues and/or for making it easier to organize complex processes. It would require outputting results to static files and it would take longer to process than the standard approach, but that is an expected trade-off.  Offering a GUI drag-drop "orchestrator" to tell Designer the order of operation would be even better than having to manually open each workflow and tell it which workflow to kick off next.

Idea

I feel the necessity of the features to know the version of Alteryx Designer Desktop for each user within an organization. 

As well as some usage data of each user like 'Last Used' are available in License Portal, if 'Version of Alteryx Designer Desktop' for each user is also available in License Portal, it would be more manageable and could enhance the governance in organization.

Background

When the organization uses Alteryx Server and Designer Desktop, it is more challenging to make alignment of version of these products.

We frequently see our users install/upgrade to newer version of Alteryx Designer than that of Alteryx Server, and cause incompatibility issue when interacting with Alteryx Server.

Although we instruct our users to install the particular version, they sometimes upgrade to newer version later on by themselves, but it's not detectable.

I mean, even if they're using a wrong version of Alteryx Designer Desktop, we won't realize it until a problem occurs.

In order to identify such users and rectify their version, administrator shall be able to know which version they use whenever needed.

License Portal would be one of the best platform to make that information available in my opinion.

Hello all,

I'm currently learning Pythin language and there is this cool feature : you can multiply a string

Pretty cool, no? I would like the same syntax to work for Tableau.

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

The Formula Tool does a good job of autocompleting expressions (for example an open square bracket will show you variables in your dataset), as well as syntax highlighting (coloring variables, keywords, strings, etc).

I propose having this feature available in all tools that use the expression editor, particularly common ones such as the Multi-Row Formula Tool and the Multi-Field Formula Tool.

This parity across tools would provide a more consistent experience for the user and increase one's productivity using these tools. It's incredibly helpful for beginners and seasoned Alteryx users alike and should be available wherever possible.

Similar to this idea, I think it would be really helpful to be able to search for fields in the dropdowns when using the Sort tool. Having to scroll through all of the possible field names can be a chore if you have 50+

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.

Description:

Currently, when running a workflow in Alteryx that writes output to a file (e.g., Excel), if the target file is already open (such as being open in Excel), the workflow will proceed through all steps and only fail at the very end when it attempts to write to that file.

Problem:

This behavior is inefficient and frustrating, especially with large workflows. You only find out there's a problem after all the upstream processes have already run. It wastes time and compute resources, and it can also be confusing for less experienced users.

Suggested Improvement:

Alteryx Designer should prevalidate output file accessibility at the beginning of workflow execution. Specifically:

Check if the output files are locked or otherwise unavailable before starting the run.

If any output file cannot be written to, immediately halt the workflow with a clear, early warning. 

Optionally, display a prompt listing which outputs are unavailable and why.

Benefit:

This enhancement would save users significant time, reduce confusion, and improve user experience, especially in development or iterative testing workflows. It aligns with good design principles by failing fast and providing immediate feedback.

Hello all,

As of today, when you want to retrieve or create a file on Apache Spark for Databricks, you have only two choices :  CSV and Avro

However it's clearly missing parquet file type :
-it's faster
-it's better for storage
-it's standard and already supported as input/output of Alteryx or for HDFS so doesn't seem hard to add here.

Best regards,

Simon

In the regex tool, there is a checkbox called "copy unmatched text to output".

Unfortunately, if you are using regex from within the formula tool, this is not an option. It would be helpful if this could be added as an optional parameter in the regex formula i.e: 

REGEX_Replace(String, pattern, replace, icase=1, unmatched=1)

Without this, regex outputs can sometimes be confusing, as string characters not specified by the pattern (unmatched) appear in the output. This confusion would be alleviated with the optional parameter.

The "Manage Data Connections" tool is fantastic to save credentials alongside the connection without having to worry when you save the workflow that you've embedded a password. 

Imagine if - there were a similar utility to handle credentials/environment variables. 

• I could create an entry, give it a description, a username, and an encrypted password stored in my options, then refer to that for configurations/values throughout my workflows. 
  • Tableau credentials in the publish to tableau macro
  • Sharepoint Credentials in the sharepoint list connector
• When my password changes I only have to change it in one place
• If I handoff the workflow to another user I don't have to worry about scanning the xml to make sure I'm not passing them my password
• When a user opens my workflow that doesn't have a corresponding entry in their credentials manager they would be prompted using my description to add it.
• Entries could be exported and shared as well (with passwords scrubbed)

Example Entry Tableau:

Then when configuring a tool you could put in something like [Tableau Prod].[Password] and it would read in the value.

Or maybe for Sharepoint:

Or perhaps for a team file location:

Any of these values could be referenced in tool configurations, formulas, macro inputs by specifying the Alias and field.

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

Hello,

As of today, DCM is great to store credentials. But once we want to dive deeper in technicity, like using macros or Applications, it's really bad. One of the things I hate is that we can't retrieve any informations from the DCM connection, just the id. Not good for logs, really bad for understanding and have some conditional logic related to connection type or name.

Here an example

Nice, I managed to retrieve an id but I have no idea of what it means : what kind of connection? what's name?

Best regards,

Simon

Hello all,

We all have experienced these last years the now famous concept of hide/unhide password :
Here a few examples of it

I would like this exact principle everywhere we have a password on Alteryx.

Best regards,

Simon