ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions. Learn more here
Start Free Trial

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

I have recently started using blobs, and I've noticed that when I select 'Disable all tools that write output' that the blob output is not disabled. 

Could it be included in the tools that are disabled please?

 

@caltang thanks for supporting this.

 

Thanks

PuffinPanic

Please add a column for the "Tool Name" to the Control Container metadata output.  

This would help greatly in finding the log lines that matter!

Control_Container_Output_2025-11-19_14-33-28.jpg

 - Add "ToolName" Column to above list of messages

 

Engine_Log_Tool_Name_2025-11-19_14-33-28.jpg

As shown in the results here

Annotation_2025-11-19_14-42-44.jpg

And the Annotation window here

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.

Joins are a vital part to any analysis.  Relating data together is the backbone of bringing data together.  Currently the Join Tool allows the relating of one or many data fields that are assigned to be equal to each other (aka Equi-Join).

 

As creativity evolves and users aspire to construct more complex relationships, Non-Equi relationships become more prevalent.  What are Non-Equi relationships?  Simply put, they are Non-Equal.  Examples:

  • Field_A  <  Field_B
  • Field_C  >  Field_D
  • Field_E  <=  Field_F
  • Field_G  >=  Field_H
  • Field_I  !=  Field_J

 

Non-Equi relationships are especially useful when working with dates that fall within a range of dates contained within two other fields.

  • Example:  Target_Date BETWEEN Low_Date AND High_Date

 

Currently, to accomplish this, there are a couple options:

 

1. Generate Rows:

  • You can use the Generate Rows Tool and fill in the range of values
  • Then use the traditional Equi-Join matching the generated date to the Target_Date
  • And persist only the INNER join stream

    Lots of tools to accomplish a "simple" task

<or>

 

2.  Cartesian Join:

  • You can use the Append Tool to replicate every Target_Date onto every row containing the Low_Date and High_Date fields
  • Filter where the appended Target_Date is between the Low_Date and High_Date

    Memory intensive, creating many unnecessary data rows, and may ultimately not work with large datasets

 

 

A simple solution, or alternative, would be to enhance the existing Join Tool to allow for choice in the "Join by Specific Fields" configuration section.  For example:

 

jrlindem_0-1761703174606.png

 

Adding in a drop-down menu per field pairing, the additional Non-Equi options could be added.  Equal would be the default, but users could otherwise pick the relationship type to accomplish the same "between" condition.

 

Here's a zoomed image of the look and feel:

jrlindem_3-1761703769943.png

 

 

The benefit is a much simpler configuration within the workflow, avoiding extra tools and creating a bunch of extra data rows that aren't relevant to the result.

 

If you're reading this and would like to see this enhancement to the JOIN Tool, consider a quick click on the like button.  It helps ideas like this get more exposure and lets Alteryx know this is important to you!

 

Cheers and thanks for taking the time to consider this idea!  -Jay (jrlindem)

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

Acknowledgements:

 

It's important for me to point out that this isn't the first time this idea has been posted.  There are others that share the sentiment for both Non-Equi Joins as well as other enhancements to the join tool.  Here are two other, older, ideas that share some of the same needs:

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. 

My company is moving off of network drives into the cloud. There is currently no tool that can write an Excel file into SharePoint with a header snippet, with formatting or with multiple Excel sheets like the Render tool. I don't know how I can remediate my existing workflows without such a tool.  

When the name of a field is changed early in a workflow, all corresponding tools that use the renamed field should have the option to auto update the field name. This way I don't have to manully update the name of each effected field. 

 

 

Hi everyone! I have been trying to find a way to do this without creating a new idea, but I have decided to make it an official 'Idea' to see if there is anyone else that might appreciate a feature like this (or has found there own way to do it!)

 

Do your workflows look like this...

 

cable mgmt idea (before).png

 

but you wish they could look like this?

 

cable mgmt idea (after).png

 

Well... they can with your help!

 

Okay, I might be crazy...but its worth a shot.

 

While I understand this is an extremely niche issue, in my experience, it can become very difficult to trace the data through unmanaged lines in large workflows. I think it will be great to cable manage canvas lines so workflows are easier to follow. Heck, while I am already at it, I think it we should all start calling these canvas lines cables... They don't carry electricity, but they sure do carry data!

 

Here is an example I created in Alteryx using select tools and containers:

alteryx cable mgmt idea.png

 

 

We can Cache and Run Workflow for individual input tools now. Why not let there be a default option to just do it automatically? Or a Run & Cache feature next to Run?

Similar to the setting that you have in many individual tools  (join, append, select, et al) where you can go to options and choose to "forget missing fields" it would be nice where you could go to options for the entire flow and "forget missing fields".

 

This would remove the headache that you have with large flows where you make a change(s) then have to go back through each and every tool to "forget" within that tool. Yes you could still do it individually, but if you chose, you could also do it universally for the entire flow all at once to all the 'missing fields'. 

Hello Together,

 

I have the following situation:

I have a workflow which is used in many different collections because of different users, regions etc,

Depending on the collection name from which the WF was started I would like to have different start parameters, different defaults for interface settings, use formulars, filters etc., having a system constant like [Engine.WorkflowFileName] but as [Engine.WorkflowCollectionName] would be great!

At the moment, I need to save the WF n-times just because of different settings instead of having just one working dynamically depending on the Collection name. Would save a lot of admin time just changing one WF instead of n!.

In case of any questions, pls. go ahead and get in touch with me!

Hello,

Right now you can write a file into sharepoint. However, sometimes, you just want to upload a file. There is already the ability to download (for Sharepoint input). I would like the same for uploading a file (based on an path or workflow dependancies).

Best regards,

Simon

A client just asked me if there was an easy way to convert regular Containers to Control Containers - unfortunately we have to delete the old container and readd the tools into the new Control Container.

 

What if we could just right click on the regular Container and say "Convert to Control Container"? Or even vice versa?!

In the 20 years of my career I have built many automations using many tools. Alteryx is one of the best but lacks a key function that many others have. The File Browse Tool and the Folder Browse tool should be able to be configured with default values.

 

There should be an option under the File Specification that says "Default Location". When the user clicks browse button in the Analytical Interface it should default to opening that location ( eg.. \\ShareDrive\Reports\Finance\ ). If this location in inaccessible by the user or Account running the job then either an error should be thrown and the flow stopped or a default location open as in 2024.2

 

Users have requested this as when you have a large network browsing to the file you need can be slow and cumbersome. Ideally we should be able set the default location in the Designer to the folder where the file they want "most likely" is. Saving the user time and effort. This same concept applies to Folder Browse.

 

Screenshot 2025-05-28 130534.png

 

The funny part about this is when you ask Alteryx Co-Pilot  (or ChatGPT, or Microsoft Co-Pilot) how to do this. Even it figures this was a option that exists.  

 

 

Screenshot 2025-05-28 131332.png

Currently if I have a connection between two tools as per the example below:

cgoodman3_0-1674567563258.png

I can drag and drop a new tool on the connection between these tools to add it in:

cgoodman3_1-1674567618537.png

 

And designer updates the connections nicely, however if I select multiple tools and try and collectively drop them inbetween, on a connection then it won't allow me to do this, and will move the connection out of the way so it doesn't cause an overlap.

cgoodman3_2-1674567779868.png

Therefore as a QoL improvement it would be great if there was a multi-drop option on connections between tools.

 

 

Block-Until-Done could be improved through adding time delay option settings between steps 1,2 and 3. An Excel workbook, for example, must be opened and closed before it can be reread or multiple tabs appended which takes time for a computer to process. Often a workaround or custom macro must be used to account for this time delay. A time delay feature directly in the tool would enable a user to customize the delay period between steps and allow for functions external to Alteryx to complete before next step is taken without macros or workarounds. If no option(s) is selected, default parameters would apply.

Currently, the Alteryx Designer canvas can only be extended to the right and downward. This restriction makes organizing complex workflows more difficult, especially when trying to insert new logic upstream or manage spatial layout more naturally. It forces users to design in a constrained directional flow, limiting flexibility and sometimes resulting in awkwardly stretched workflows.

 

Proposed Solution:
Introduce an Infinite Canvas option that allows users to pan and place tools in any direction: left, right, up, or down. This would:

  • Enable more natural workflow layout and organization
  • Allow insertion of tools before existing logic without major rearrangement
  • Improve visibility and navigation for large, complex workflows
  • Mirror the functionality of modern visual tools like Figma, Miro, or Lucidchart

 

Bonus Suggestion:
Include a toggle or setting in Preferences to enable Infinite Canvas mode, so users can choose their preferred design behavior.    

 

Impact:
Improved usability, better layout control, reduced time spent reformatting workflows, and a more modern, flexible design experience for Alteryx users at all levels.

In the tools that embed the "Rename" option (Select, Append Fields, Join, Join Multiple), copying the new name will copy all the information of the field configuration : tick/untick, original field name, type, size, new name and description.

 

Renaming the field "Rename_Field"Renaming the field "Rename_Field"

 

 

Capture2.PNG

 

In my opinion, it should copy only the new name. This would be useful, especially because when you change the name of a field, it isn't automatically changed in subsequent tools, so copying it to replace it in those tools is faster than retyping it every time.

The TO field (and I assume other fields) in the Email tool seem to have a 254 character limit - this should be increased heavily as there are many distribution lists that will go above this character limit!

A distribution list works but is not ideal. Thumbs up if you like this idea!

The idea is quite simple. I am sure a lot of Alteryx enthusiasts use containers frequently. These can also be color coded for better overview and readability of your workflows. However, while connections between tools can be named, they cannot be colored. 

 

Therefore, this idea is very simple. Adding an option to color these connections. This would allow for even more readability of workflows. Especially if a workflow contains multiple separate streams of data, this could help to navigate and keep track of how and where data is flowing.

 

 

 

Idea_ConnectionColors.png

Top Liked Authors