Alteryx Designer Desktop Ideas

Currently when a unique tool is used, and a field is removed upstream then the workflow fails to move forward. If you have one or two unique fields being used then it is no big deal, but when you have a very complex workflow then you have to click into each one of those tools in order to update. This can be very problematic and creates a lot of time following all the branches that is connected after the 1st unique tool is used. My suggestion is to make this a warning instead of a fail or have an option to select fail or warning like the union tool is setup. This way people can decide how they want this tool to react when fields are removed. 

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,

As of now, you can't choose the DCM connections to synchronize. It's either all or none.

However, I have one designer and two servers (Sandbox/Production). Most connections must be common, but not all.

Best regards,

Simon

The idea behind encrypting or locking a workflow is good for users to maintain the workflow as designed. 

However, when a user reaches a level of maturity equivalent to that of the builder or more, or even when changes are required - the current practice is to keep a locked and unlocked version of the workflow so that it allows for a change in the future. 

It would be much simpler if we can have the power to lock and unlock workflows with a password. Users can then maintain and keep the passwords so that they can continue with the workflow. 

Not everybody is on Server yet so this feature is very helpful for control before Server migration. Otherwise it’s just password protecting a folder containing the workflow package, then re-locking a new save file each time a change is made or when someone new takes over on prem. 

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.

We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.

I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.

The basic concept behind this idea is to allow us (users) to have:

• Design Patterns
  • Repetitive patterns to be reusable.
  • Select after and Input tool
  • Drop Nulls
  • Get not matching records from join
• Conditional execution
  • Tell Alteryx to execute some logic if something happens.
  • Record count
  • Errors
  • Any other condition
• Order of execution
  • Need to tell Alteryx what to run first, what to run next, and so on…
  • Run this first
  • Execute this portion after previous finished
  • Wait until “X” finishes to execute “Y”
• Orchestration
  • Putting all together

This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:

The approach is to extend Tool Container’s attributes.

This proposition uses actual functionalities we already have in Designer.

So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:

1. Refers to the actual interface of the Tool Container.
2. Provides the ability to disable a Container (and all tools within) once it runs.
   • Idea based on actual behavior: When we enable or disable a Tool Container from an interface Tool.
3. Input and output data to the container’s logic, will allow to pickup and/or save files from a particular container, to be used in later containers or persist data as a partial result from the entire workflow’s logic (for example updating a dimensions table)
   • Based on actual behavior: Input & Output Data, Cache, Run Command Tools, and some macros like Prepare Attachment.
4. Order of Execution: Can be Absolute or Relative. In case of Absolute run, we take the containers in order, executing their contents. If Relative, we have the options to configure which container should run before and after, block until previous container finishes or wait until this container finishes prior to execute next container in list.
   • Based on actual behavior: Block until done, Cache, Find Replace, some interface Designer capabilities (for chained apps for example), macros’ basic behaviors.
5. Conditional Execution: In order to be able to conditionally execute other containers, conditions must be evaluated. In this case, the idea is to evaluate conditions within the data, interface tools or Error/Warnings occurrence.
   • Based on actual behavior: Filter tool, some Interface Tools, test Tool, Cache, Select.
6. Notes: Documentation text that will appear automatically inside the container, with options to place it on top or below the tools, or hide it.

This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:

I'm looking forward to hear what you think.

Best

Hello all,

It's really frustrating to have an "alteryx field type" in In-Database Select. It doesn't even make sense since we're manipulating only data in SQL database where those types does not exist. What we should see is the SQL field type.

Best regards,

Simon

Currently it's not possible to "switch off" interface tools in the same was as we can with the other tools. This limits the functionality especially within chained apps. If we could switch these tools off it would be much easier for us to tailor the experience by allowing selections to be activated by logic, rather than simply the data therein.

Please Alteryx Gods. I beseech thee!

*lights candles*

Hey all,

I don't know about you, but I have always had trouble hovering the mouse over the Results window pane trying to get the resize icon to appear. It seems like you need surgeon level precision to find the icon! 😷

I love Designer and want to see it be the best it can possibly be. I feel like increasing the clickable/hovering area for this resize would be amazingly helpful! 

Just wanted to see if we could get some community momentum going in order to get some developer eyes on this issue. 🙂

 Please help by bumping/upvoting this thread!

 -K

Migrated this from another thread. Some folks tagged from the original post :)
@cpatrickwk @caltang @afellows @MRod @alexnajm @ericsmalley @MilindG @Prometheus @innovate20 

Adding a up and down arrow on each column would make it easier and quicker to sort columns then the drop down menu or sort tool

Additional Dynamic Select Mode for All Native (Non-Macro) Tools with Select Functionality (with or without Data Type Selection)

This is the updated version of an idea I posted a while ago (which only included Multi-Field Formula), and after the release of Alteryx Designer 2025.1, which I found to be very successful from a new tool and functionality perspective, I decided to post about it.

My proposition is to add the Dynamic Select functionality* (at least the Select via a Formula mode) to all native (non-macro) tools in all tool categories that include a Select functionality (as an alternative, where the user would be OK with not being able to also change the field types of the selected fields, such as Join and Append tools, the opposite would apply to Multi-Field Formula, where the user would be able to dynamically select which fields the Multi-Field Formula would be applied to, in addition to changing the data type), including but not limited to (to account for any new tool with a Select functionality that might be added in the future):

Preparation Category

- Auto Field

- Data Cleanse Pro (added in 2025.1)

- Multi-Field Formula

- Multi-Row Formula (for Group By option)

- Rank (for Group By option)

- Record ID (for Group By option)

- Sample (for Group By option)

- Tile (for Group By option)

- Unique

Join Category

- Append Fields

- Find Replace

- Join

- Join Multiple

Transform Category

- Arrange

- Cross Tab

- Make Columns (for Grouping Fields (Optional) option)

- Running Total (for both Group By (Optional) and Create Running Total options)

- Transpose (for both Key Columns and Data Columns options, the tool would generate an error if the Dynamic Select formula written for both options are selecting the same field(s), as the Transpose tool is not supposed to allow it)

- Weighted Average (for Grouping Fields (Optional) option)

In-Database Category

- Select In-DB

Reporting Category

- Layout (for Group By and Per Column Configuration options)

- Table (for Group By and Per Column Configuration options)

Machine Learning Category

- Transformation (for Select Features mode only, as the other two modes with Select functionality (Clean Up Missing Values and One Hot Encoding) require Method and Missing Category Action specification)

Developer Category

- Download (for And values from these fields option present in Headers and Payload tabs)

- Dynamic Rename (for the Select functionality present in Formula mode)

Spatial Category

- Find Nearest

- Spatial Info

- Spatial Match

Data Investigation Category

- Pearson Correlation

Skipping Address and Demographic Analysis categories as they have tools that seem to be using a static input, therefore not requiring a Dynamic Select functionality.

Laboratory Category

- JSON Build (for Grouping Fields (Optional) option)

- Transpose In-DB (with a similar logic to the regular Transpose tool found in Transform category)

*The Dynamic Select functionality added tools that have more than one input anchor (such as Join and Join Multiple) could have new additional fields the users can utilize, such as:

- [Origin] (can have the values "L" or "R" for Join and Append tools)

- [Connection_ID] (can have the values 1, 2, 3 etc. for Join Multiple tool)

- [Unknown] (can have the values "True" or "False" for the Data Columns option of the Transpose tool, or any other tools such as Join that would have the Dynamic or Unknown Columns option as a part of their Select functionality)

Dear Alteryx, 

One day, when I pass from this life to the next I'll get to see and know everything!  Loving data, one of my first forays into the infinite knowledge pool will be to quantify the time lost/mistakes made because excel defaults big numbers like customer identifiers to scientific notation.  My second foray will be to discover the time lost/mistakes made due to 

Unexpanded Mouse Wheel Drop Down Interaction

Riveting right?  What is this?  It's super simple, someone (not just Alteryx) had the brilliant idea that the mouse wheel should not just be used to scroll the page, but drop down menus as well.  What happens when both the page and the drop down menu exist, sometimes disaster but more often annoyance.  Case in point, configuring an input tool.

See the two scenarios below, my input is perfectly configured, I'll just flick my scroll wheel to see what row I decided to start loading from 

Happy Path, cursor not over drop down = I'll scroll down for you ↓

Sad Path, cursor happened to hover the dropdown sometimes on the way down from a legit scroll = what you didn't want Microsoft Excel Legacy format?

And you better believe Alteryx LOVES having it's input file format value changed in rapid succession., hold please...

Scroll wheels should scroll, but not for drop down menus unless the dropdown has been expanded.

Oh and +1 for mouse horizontal scrolling support please.

Hello,

A lot of tools that use R Macro (and not only preductive) are clearly outdated in several terms :
1/the R package
2/the presentation of the macro
3/the tools used

E.g. : the MB_Inspect

Ugly but wait there is more :

Also ; the UI doesn't help that much with field types.

Best regards,

Simon

Hello! It would be great if I could "favorite" a tool when I search for it in the search bar in Designer. Currently, I can drag and drop it to the Canvas, but if I want to "favorite" it, I have to remember the icon and color, then go find it in the right tab. This would be a nice enhancement!

Sounds simple :

Best regards,

Simon

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

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!

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.

Everyone knows the importance of adding the appropriate controls and governance to your workflows - and often, this means including events that will generate notifications if a workflow is running with errors.

But who is the audience of that email? If it's not a developer, will that person know what they are reading and where to focus?

How about a developer that would like to customize the message that the end user will receive?

Porting some existing functionality from other tools in the Alteryx toolkit to the Events page could easily provide added flexibility to event generation:

1) Add a formatting bar to the tool like shown in the image below

-- Style changes

-- Alignment

-- Highlighting

-- Coloring

-- Images

2) Add a function bar to the tool like shown in the image below

-- Ability to view all available variables

-- Ability to apply formulas using variables

-- Ability to save formulas

What do you think? Give this post a thumbs up if you find the post helpful!