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

Hello,

Here is the proposal about an issue that I face frequently at work.

 

Problem Statement -

Frequent failure of workflows that have either been scheduled or run manually on server because the excel input file is sometimes open by another user or someone forgot to close the file before going out of office or some other reason. 

 

Proposed Solution - 

The Input/Dynamic Input tools to have the ability to read excel files even when it is open so that the workflows do not fail which will have a huge impact in terms of time savings and will avoid regular monitoring of the scheduled workflows.

 

 

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.
alteryx_monetdb2_.png
Best regards,

Simon

Documenting your Alteryx workflow is important because it allows others to understand and modify it as needed. To document your workflow effectively, you should provide detailed information about your inputs, outputs, tools used, and any assumptions or limitations.

 

When it comes to documentation, annotations are often more practical than the comments tool. However, the comments tool in Alteryx offers a useful feature that allows you to customize the background, font, and border colors. These customizable colors can be beneficial when reviewing workflows, as they help draw attention to specific details or notes.

 

In the screenshot below, you can observe that the highlighted comment attracts more attention compared to the annotation on the left side, even though they contain the same comment.

 

It would be great if the color customization features available in the comments tool could also be added to the annotations of any tool.

 

SaadNaser_0-1684052340300.png

 

 

 

The JOIN tool could use some love.  Let's consider merging the JOIN and UNION functions into a single tool.  Instead of strictly L, J, and R outputs, we could have an option to allow for all standard SQL joins:

 

  • Cross Join (Warning!!!)
  • Inner Join (boring)
  • Left Outer Join (saves time configuring Union)
  • Right Outer Join (saves time ...)
  • Full Outer Join (saves time ...)

Being able to JOIN on case-insensitive values is a big bonus (resisted urge to BOLD and change font size).

Being able to JOIN on date-range is often requested.

Being able to JOIN on numeric-range is often requested.

 

If we are combining tools, getting UNIQUE on L or R (or both) inputs would also save time.  Most JOIN errors are because the incoming (R) data contains duplicates by KEY.

 

cheers,

 

Mark

 

Hi @NicoleJ 

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.

To allow users to pull data from Power BI, eg. datasets and usage data, to allow it to be manipulated in Alteryx. 

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.

 

image.png

Best regards,

Simon

 

 

We all know and love the Comment tool. It's a staple of every workflow to give users an idea of the workflow in finer details. It's a powerful tool - it helps adds context to tools and containers, and it also serves as an image placeholder for us to style our workflows as aesthetically pleasing as possible.

 

Now, the gensis of this idea is inspired by this post and subsequent research question here.

 

The Comment Tool today allows you to:

  • Write your text and provide context / documentation to your workflow
  • Style its shape
  • Style its font, colour, and background colour
  • Align the text
  • Put an image to your workflow

image.png

 

But it would provide way more functionality if it had the capabilities of another awesome Alteryx tool that is not so frequently mentioned... the Report Text Tool!

 

What's missing in the Comment tool that the Report Text tool has?

  1. The ability to add active data records from the workflow to its text
  2. Its wider range of styles which allows for more functionality such as with its Special Tags functions
  3. Its ability to hyperlink
  4. Text mode options!

image.png

 

Now, whilst I understand that the Report Text tool is just that, a tool that needs to be connected to the data to work, so too does the Comment tool (to a lesser extent).

 

It would be awesome to have the ability to connect the data to the Comment tool as it was a Control Container-like connector. It can also be just like the Report Text tool with an optional input, thereby making it like a normal Comment tool.

 

To visualize my point:

image.png

 

The benefits of doing so:

  • Greater flexibility to the user
  • Styles are endgame
  • Users can use the comment box as a checksum or even a total count / checker to ensure everything is working as intended
  • Makes the comment tool more powerful as a dynamic workflow documentation tool

I think it'll be a killer feature enhancement to the comment tool. Hoping to hear comments on this! 

 

Kindly like, share, and subscribe I mean comment your support. Thanks all! 😁

 

-caltang

My idea is essentially to borrow the keybinding/command ethos of Vim for Alteryx. For those who are unfamiliar, Vim is a text editor from a time before the mouse and the GUI became dominant forms of interacting with PCs. I think the key ideas to take from Vim are the Modes, Commands, and Grammar.

 

Vim is mode based for its typing. You start out in Normal mode and enter other modes through key commands. For example, to enter Insert mode, you just type 'i'. This mode allows you to enter text into whatever file you have open at the moment. There's also the Visual mode which is for highlighting sections of text for processing with other commands. This means that key commands can take on a variety of meanings in different modes, adding depth in a limited key range.

 

The Grammar is another key aspect. Rather than hold an arcane combination of modifiers and letters, Vim uses an Operator-Count-Motion approach. The operator will be the primary action: y for yank/copy, d for delete, c for change, v for visual select. The Count is how many objects you want this operator to be applied to. The Motion is where and what you want to work with: w for a word, s for a sentence, p for a paragraph, ( for a set of parentheses, b for brackets. There are also options that extend this so you can have a series of commands like d2w (delete 2 words), di( (delete inside parentheses), yap (yank/copy all of a paragraph), etc. Below is a cheat sheet displaying a wider list of the possibilities with the motions.

 

0edc98b0-6f9f-4a17-8d9f-7a9655cd9fbe.png

 

The Command mode is the last piece of the puzzle. By typing ':' while in Normal mode, you bring up a command prompt. Here you can enter any of a number of commands including changing user settings via keywords. For example, :s/old/new/gc will search through my file and attempt to find and replace every old term with the new term, the c at the end means that Vim will ask for confirmation before each change. I could also do things like :set nohl which will turn off highlighting for items found during searches. It's easy to imagine using similar functionality to make configuration changes to a wide set of tools or simply to selectively delete tools without using the mouse or scrolling to them.

 

To take it a step further, current menu functions could be turned into commands, imagine typing v6t to select the next 6 tools on the canvas. You could follow this by typing :Contain %V to wrap the selected tools in a container, perhaps with extra arguments a specific color palette could be applied as well! I say all this to say that the way forward for shortcuts in Alteryx is to break away from the one-handed modifier heavy paradigm that so many programs follow today. By creating commands that can duplicate the actions found in drop down and right click menus, as well as providing a means of navigating the canvas without a mouse, Alteryx can go to the next level in terms of efficiency and ergonomics.

 

Let me know what you think, if you need more concrete ideas on what this might look like in practice, I can add that. Thanks!

 

P.S. If you work on side projects outside of Alteryx, consider giving NeoVim a try, it adds a lot of extensibility and customization to classic Vim

Hello all,

I really appreciate the ability to test tools in the Laboratory category :

simonaubert_bd_0-1672223871200.png



However, these nice tools should go out of laboratory and become supported after a few monhs/quarters. Right now, without Alteryx support, we cannot use it for production workflow.

simonaubert_bd_1-1672223991592.png



Example given :
Visual Layout Tool introduced in 2017
https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Tool-Mastery-Visual-Layout/ta-p/835...

Make columns Tool also introduced in 2017
https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Make-Columns-Tool/ta-p/67108

Transpose In-DB in 10.6 introduced 2016
https://help.alteryx.com/10.6/LockInTranspose.htm

etc, etc...

Best regards,

Simon

Sounds simple :

 

image.png


Best regards,

Simon

Hello all,

This is a very interesting feature of the List Box and Drop Down interface tool : the ability to select fields

image.png

image.png

However such a feature is not available for in-database, highly limiting the use of macros.

Please change.

Best regards,

Simon

Connecting to Smartsheets using Alteryx Desktop (and by extension, Alteryx Server) is extremely cumbersome. If a user wants to read data from Smartsheet, they are required to get an API token (preferred) or use a username/password

 

Then do one of the following to read data from Smartsheets:

1. a. Install a ODBC driver

    b. Configure a DSN connection for ODBC
    c. Use the input data using a generic ODBC connection
or
2. Use python

 

To write data to Smartsheets, a user can use Python or upload the data using an API call - both very hard for end users to use especially if they're not Python developers.

 

Regardless, all of these are problematic. On the server I manage, I have over 15 ODBC connections to Smartsheets and it's getting very hard to upgrade the server hardware because of them. Creating a native connector for input/output of data to Smartsheets will eliminate a headache of managing ODBC connections, and make it simple for Alteryx Desktop users to read and write data.

 

 

A very useful and common function
https://www.w3schools.com/sql/func_sqlserver_coalesce.asp

Return the first non-null value in a list:

COALESCE(NULL, NULL, NULL, 'W3Schools.com', NULL, 'Example.com')
returns 'W3Schools.com'

It exits in SQL, Qlik Sense, etc...

Best regards,

Simon

Please add a toggle for Dark Mode as Alteryx, after all these years of using it, is burning out my retinas. 

 

The OS and most apps have a Dark Mode theme so flipping back to a bright white canvas is very jarring.  I tried to adjust the canvas colors in a more muted way but never can get it to work satisfactorily and still be as easy to read as the retina burning default.  

 

There is no tool that exists that outputs all records that are duplicates (those sharing the selected values with at least one other record) and also outputs the records that are not duplicates (those not sharing the selected values with at least one other record).

 

The Unique Tool is not sufficient.  It only provides the first record of a unique duplicate group along with any non-duplicates and then provides a secondary output that only contains the additional records of a duplicate group.  Sometimes you only care about the duplicates and want to quickly see what differs between the unique groups.

 

For example, if there are 4 records with the City of Austin and I am looking for duplicates on City I want to see all 4 records with Austin in the output so I can quickly compare additional fields to see what might differ, or if they are all indeed truly duplicates.

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*

I am aware that an Auto-Documenter tool is available in the Gallery, but that has not been maintained since 2020. 

 

It would be great if Alteryx could have that as an added feature to the Designer as an option for end-users to utilize. 

 

The breakdown of it can be done via XML parsing as such: 

<Nodes>: Configuration of tools

<Connections>: The tools used

<Properties>: Workflow properties

 

Right now, the current workaround is for users to export their XML, and the internal Alteryx development team has to build another workflow that reads the XML accordingly + parses it to fit what is needed. 

 

It would be better for Alteryx to build something more robust, and perhaps even include some elements of AiDIN which they are promoting now.

Hello,

It's nice to have this OpenAI Connector but it seems it must be the default OpenAI URL. In my company, we use OpenAI on an Azure instance and I'm unable to connect to it.

(by the way, I know pre-sales teams have developed lot of connectors for fireworks, mistral, etc.. it would be very cool to have it available).

Best regards,

Simon

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

 

Events.JPG

 

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

Top Liked Authors