Alteryx Designer Desktop Ideas

When making any type of macro, it's important to test the functionality of the macro via a debug.  This is accomplished successfully with normal tools, however there's a bug that will not allow the user to debug In-DB macros that use either of the following standard Alteryx tools:  

• Macro Input In-DB
• Macro Output In-DB

If either of these tools are included in the macro you are building, an error message will appear not allowing you to open a debug.  

Error message: Question Tool Load Error:  A question tool with a tool id of XXX is missing the associated question data.

Of course, Macro input and output tools do not require any specific action/question tool associated with it.  This is a bug.  A user pointed out the XML issue almost 3 years ago here:

In summary: "It appears that the tool itself inserts a hidden Question attribute into the XML which can also be seen in Workflow Configuration"

Source:

https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/In-DB-Macro-Input-and-Output-t...

Examples....

A normal macro, using standard tools:

After debugging a standard macro, the Macro Input/Output tools correctly change to a Text Input and a Browse tool.  This allows the macro author to test the macro.

However, when trying the same thing with In-DB tools in a macro, an error message appears:

In-DB macro 1:

In-DB Macro error message (after clicking "Open Debug"):

Hello,

Working on Dataiku DSS and there is a cool feature : they can tag tools, parts of a worklow.. and then emphasize the tools tagged.

Best regards,

Simon

Right now, the List Box interface tool allows end users to select multiple options of fields for selections, filtering, and formatting/formulating. 

However, it doesn't do quite as good when a use case has over 1,000+ columns/fields. This is made even more complicated with each column/field having somewhat similar naming conventions thereby causing confusion. 

Having a search function, as made available in standard Select Tools, Join tools, and other tools that has filtering capacity, will be most helpful for developers to give maximum flexibility to end users.

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!

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

Hello all,


As of today, we use the good old alias in-memory to connect to our datasources in in-memory. We have several environments so we use constants in order to change the name of the in-memory alias during execution.

To illustrate :

Depending of the environment, the constant « v_gp_contexte » will take different values :

• GP_DS08_SIDATA for la dev.
• GP_EE_SIDATA for prod.

Sounds nice, right? But now, we would like to use DCM and the nightmare begins :

We can't manually change the name and set the question :

if we look at the xml of the workflow, we only find an id so editing it is useless :

(for informationDCM connections are stored in some sqlite db in C:\Users\{yourname}\AppData\Local\Alteryx

So, I would like to use the DCM inside the in-memory alias (the in-memory alias is stored and can be edited), just like for in-db connection alias.

Best regards,

Simon

How about a “Temporarily Disable Tool” feature where the tool is disabled?  Just the same as the "Disable All Tools that Write Output" but would only apply to the specific tool you select.   But, Instead of having to delete or cut the tool and connect around (as this can be tedious)!  The feature could be applied to various preparation tools (and potentially more) to help save time.

For example, there are occasions when I might have a filter applied and would want to temporarily disable the tool only to see all results.  This has been the case when I have wanted to include hospital wards (by temporarily disabling the tool) I was filtering out to review in the summarized totals.

The specific tool could have the same hashed marking as the "Disable All Tools that Write Output".   The "Temporarily Disable Tool" feature could be listed when the specific tool is right clicked on.   - The workflow could also prompt to show that the user has a tool "disabled" to highlight to the user.

Edit: Spelling

This is a feature request based on my comment submitted here: Email Tool: Format "From" field to accommodate "Di... - Alteryx Community

It would be great to provide an option in the Designer Email Tool to allow us to specify a "Display Name" when sending emails.  The "Display Name" is a common part of the email specs listed here: RFC2822 - Section 3.4 (Address Specification) 

The email gateway/service that I'm using will send emails, but the "From" line will reflect only the email address.

For example, it will show an email as being from "john.smith@example.com" where I would love for it to show up as from "Smith, John".  This would make emails appear like other internal company emails in our company Outlook clients, and in general provides more useful flexibility for the Email tool. 

Many other email clients support using Display Name, but it appears that Alteryx currently doesn't.

The format of an email address with Display Name is something like "Smith, John" <john.smith@example.com> (with or without the quotes).

Sounds simple :

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!

Hello all,

Apache Doris ( https://doris.apache.org/ ) is a modern datawarehouse with a lot of ambitions. It's probably the next big thing.

You can read the full doc here https://doris.apache.org/docs/get-starting/what-is-apache-doris but to sum it up, it aims to be THE reference solution for OLAP by claiming even better performance than Clickhouse, DuckDB or MonetDB. Even benchmarks from the Clickhouse team seem to agree.

Best regards,

Simon

The Find Replace tool has a checkbox to do a case insensitive find. It would be fabulous if the Join and Join Multiple tools had a similar checkbox.

I frequently have to create a new field in each data stream, convert the data I want to join on to upper case, perform the join and remove the extra "helper" fields. Using the helper field is needed in my case in order to preserve unique capitalization (i.e., acronyms within the string, etc.). 

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

Hi there

My idea is to have an option to copy and paste a tools configuration to a different tool of the same type somewhere else on the canvas.

Example:

Say I have four summarise tools dealing with four different data streams, I envision a 'Copy Tool Configuration' option after right clicking on a tool and then a 'Paste Tool Configuration" which can be applied across the multiple instances of the summarise tool by overwriting. This would preserve the tools anchors incoming and outgoing connections.

Benefit:

This would increase the speed of developing workflows. Naturally this would be significantly quicker than copy and pasting tools, and then re-wiring anchors. Additionally, this would potentially reduce human error when iteratively developing workflows.

Regards - Rhys Cooper

In the RecordID tool,  provide additional options for the creation of the ID, specifically allow for the ID to 'Intervals'. 

For example, Record ID every 10, meaning instead of creating an ID of 1, 2, 3, 4, 5 .... you could create an interval of your choosing, the most obvious would by 10 or 100  thus your ID's would then be 10, 20, 30, 40 ....  or  100, 200, 300, 400, 500 ... etc. 

Ability to ‘name’ the point created in the “Create Points” tool.

Instead of sticking a select tool after it to rename it from ‘centroid’ to Starting Location or Store location or whatever.

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. 

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.