Inspire EMEA 2022 On-Demand is live! Watch now, and be sure to save the date for Inspire 2023 in Las Vegas next May.

Alteryx Designer Ideas

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

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

Submission Guidelines

Featured Ideas

SOOOOoooooo many times it'd be great to just dictate the character length/count (fixed width) for the parse (just like you can in excel), instead of being constrained by a delimiter or being obligated to go create (potentially complex) REGEX.  Ideally you could go into the column and insert the <break> (multiple times if needed) after the given character where you'd like the parse to occur.  Anything past the last <break> would all be included in the final parse section/field. 

You could also do it a little less visual and just identify/type the character count you want for each column.  If you really want to enhance this idea, you could also include the ability to name the fields and prescribe the data type.  Those would just be gravy on the meat of the idea however, which is, provide the ability to parse by fixed length fields.





In Japan, the prople usually use the date format "yyyy/mm/dd". But there is no preset in Date tool. So I usually use custom setting, but it is the waste of time.


So please add yyyy/mm/dd format to the preset in Date tool configuration for Japanese people.




It would be absolutely marvellous if the ability to use a field as the replace value could be incorporated into the Regex tool. Currently the "Replacement Text" field is a hardcoded text value, and so to make that dynamic you have to wrap the tool in a batch and feed in the value as a Control Parameter. If we could just select a field to use as the replacement value, that would be spiffy.





We've got your metadata.  Suppose the "SELECT COLUMNT TO SPLIT" question is considered by Alteryx and this happens:


  • A field is selected because it contains similar \W (regex for non-word characters) patterns in the data (e.g. count of delimiters in the field are roughly equal).
  • The delimiter (MODE delimiter or BEST) is defaulted
  • Split # of columns = MODE count + 1

If a user updates the Field/Delimiter, the metadata could suggest the right Number of columns based upon the delimiter.


This all belongs in the automagically idea bank.  It saves me the time of counting delimiters or trial and error counts.





After using the Text to Columns tool, I generally find myself using a Select tool to get rid of the original field that I split up. Could an option be added in the config to automatically delete this field once it is split to columns?

  • Category Parse

Currently I find myself always wanting to replace the DateTime field with a string or visa verse.


It would be nice to have a radio button to pick whether to append the parsed field to replace the current field with the parsed field.


I understand that all you need is a select tool after, this would be a nice QoL change especially where the field may be dynamically updated.

Hey all,


The join tool currently does not allow case-insensitive joins, but the find/replace tool does.    Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle.    Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type


Please could you consider amending the join tool to include 3 new options or capabilities:

- Case insensitive join

- Allow full Unicode character set in join

- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value


That would remove a load of work from every text-join that's being done on every canvas we do.


Thank you 




The expression editor in the RegEx tool is only a single line, which makes it really hard to edit long regular expressions. See attached photo comparing the expression editor in the RegEx tool compared to the formula tool for the same expression. Please make the RegEx editor box either wrap to multiple lines, have a pop-out expression editor, or something so we can see long expressions.


regex idea.PNG

Hi all,

@AlexKo did an excellent article on RegEx, and Mark @MarqueeCrew Frisch has helped me out of many pickles with Regex - and one of the things that I've discussed with a few folk on the community is that Regex is super-powerful ( @Ken_Black made this same comment) and can do way more than we initially understand.


The problem is not one of the power of the tool, but rather the onramp to using it (it's painful to do/experiment/run/try etc, it doesn't give you any visual guides or hints when you've got it right or wrong, etc)


My method is to hop straight on to http://regex101, paste in sample text, and figure out the right RegEx in their AWESOME UI which really make this into a 5 minute job, and makes me feel like I've scored at least one victory today (it is so easy, you actually feel more powerful and competent).


Could we bring some of this great User Interaction design into the RegEx tool?   I honestly believe that if the RegEx tool was as easy and approachable as (or why not go one better than them), we'd see an explosion in usage and creativity.


Thank you all


  • Category Parse

When entering a number of column names in the RegEx parse mode - please can you allow either Enter or down-arrow to move down to the next cell (standard windows convention)?


Currently Enter just exists the edit mode; and down-arrow does nothing.


Annotation 2020-07-06 210535.png


cc: @Hollingsworth 

The DateTime tool is a great way to convert various string arrangements into a Date/Time field type. However, this tool has two simple, but annoying, shortcomings :


  1. Convert Multiple Fields: Each DateTime tool only lets you convert one field. Many Alteryx tools (MultiField, Auto Field, etc.) allow you to choose what field(s) are affected by the tool.  If I have a database with a large number of string fields all with the same format (such as MM/DD/YYYY), I should be able to use one DateTime tool to convert them all!
  2. Overwrite Existing Field: The DateTime tool always creates a new field that contains your converted date/time. I ALWAYS have to delete the original string field that was converted and rename the newly created date/time field to match the original string field's name. A simple checkbox (like the "output imputed values as a separate field" checkbox in the Imputation tool) could give the flexibility of choosing to  have a separate field (like how it is now) or overwrite the string field with the converted date/time field (keeping the name the same).

Alteryx is overall an amazing data blending software. I recognize that both of these shortcomings can be worked around with combinations of other Alteryx tools (or LOTS of DateTime tools), but the simplicity of these missing features demonstrates to me that this data blending tool is not sufficiently developed. These enhancements can greatly improve the efficiency of date handling in Alteryx.


STAR this post if you dislike the inflexibility of the DateTime tool! Thank you!

  • Category Parse

When copying and pasting the datetime tool, or disconnecting its input, it loses its configuration. This can be really frustrating if it has an unusual formula, and can result in looking up the datatime functions again: and working out how to reconfigure the tool.

Steps to reproduce this issue:

1.  Set up datetime tool


2. Delete Input Connector:


3. Reconnect and notice the formula is missing and it has been reset to a completely fresh DateTime Tool:


Proposed solution:
The Datetime tool should remember the previous configuration, and go back to this when the input is deleted or it is copy pasted. It will then be able to be reconnected.

Steps in proposed solution:
1. Setup Datetime tool


2. Delete input Connector (Note the DateTime Config and Annotation Remaining, but still being not editable)

3. Reconnect the tool for it to still be configured for the data

The XML Parse tool has a checkbox to ignore errors and continue.  This idea works for all options that allow you to ignore errors.  It would be great if XML Parse had 2 outputs, 1 for successful records and another for the errored records.  This would make it much easier to identify and update (if necessary) errored records.

In my view this would make it more similar to other tools like Filter or Spatial Match where records that don't fit your criteria follow a different flow.


Thanks for considering

We're currently using Regex and text to columns to parse raw HTML as text into the appropriate format when web scraping, when a tool to at least parse tables would be hugely beneficial.

This functionality exists within Qlik so it would be nice to have this replicated in Alteryx.

Obviously, we need to retain the ability to scrape raw HTML, but automatically parsing data using the <td>, <th> and <tr> tags would be nice.

In the following page there is a table showing the states and territories of the US:

States.PNGWith Qlik, you can input the URL and it will return the available tables in tabular format:


States - Qlik.PNG


As this functionality exists elsewhere it would be nice to incorporate this into Alteryx.

I love the new Custom Format option with the DateTime tool in Alteryx 11.0, this makes working with dates SO MUCH easier... BUT it would be great if you could update an existing field rather than having to create a new column (e.g. DateTime_Out) and then use a select to put this back to the original Date field.




  • Category Parse

I've been dealing with JSON since day one, and to be honest it isn't the best experience I've had.

Converting a hierarchical schema into a tabular one is't a straight forward process, but doing that everyday the old way is time and processing consuming.


What I'm proposing is a tool that can read JSON as input, then display a structural skeleton for the user, or the user can provide such skeleton for the tool, say let's say we have the following input:



{"menu": [{
  "id": "File",
  "popup": {
    "menuitem": [
      {"value": "New", "action": "CreateNewDoc", "icons": ["SAVE", "FLOPPY"]},
      {"value": "Open", "action": "OpenDoc"},
      {"value": "Close", "action": "CloseDoc", "conditions": [11,8,4]}
  "id": "Edit",
  "popup": {
    "menuitem": [
      {"value": "Cut", "action": "TextCut", icons: ["CUT", "SCISSORS"]},
      {"value": "Copy", "action": "OpenDoc"},
      {"value": "Paste", "action": "CloseDoc", "conditions": [5,17]}
"error": false




now to parse this into a table of menuitems we need to use:

  • JSON Parse: convert JSON into one long key:value table
  • TextToColumns: split key into multiple columns
  • Filter: make sure we only get one level from the tree
  • CrossTab: Convert it back into a column based key values.


All of this will give us the most primitive table we can have as:

00CreateNewDoc SAVE,FLOPPYNew
01OpenDoc  Open
02CloseDoc11,8,4 Close
11OpenDoc  Copy
12CloseDoc5,17 Paste


and now if we want to have the parent menu id along side with the menuitems, we will do that again as:

  • Filter: for parent values only
  • CrossTab: for parent values into a table
  • Join: to join Parents with Sub items and add the Parent.Id




Now all of this is done with Concatenating of child items, as cross tab will allow us to only do Concat/First/Last for items with the same grouping values.

And now if we want to process children, count them, or extract their data into another table, we have to add more Filters, more CrossTab and more Joining to get parent IDs for future linking.


So what's I'm proposing?


I'm thinking of a Tool with an interface that give me the ability to choose:

  • Target Branch: which is the main table to be extracted from the branches, in this case it would be menu->popup->menuitem.
  • Parent Values: what values to be appended from parents of the previous table, just like menu->Id and others if exist.
  • Children Data types: selecting the proper and expected data type for children instead of using strings or the existing different columns way.
  • Children Arrays Process: what to do with children branches? either stopping their process and return them as is (Stringify), exclude or do other process like count.


the tool may extract the structure or let the user input such config as the following:



Or Input the Structure as a YAML formatted config or any other way.


This will allow the user to have a quick native tool that does what he wants as it should, and user can use it as much as he want for children and nested values. you just Stringify and repeat and only parse what you need every time.


I hope you consider this for me to replace tens of macros and tools into single tools such so.


Thanks for your help and time and all the best!


  • Category Parse

Quick and (hopefully) simple one here.  Many times when I use the Text To Columns tool, there is still leading whitespace from comma separated lists with spaces.  It would save from the minor inconvenience of putting a Data Cleansing tool after each of these tools to include an Advanced Option to trim whitespace from the results.  I tried some workarounds using the empty fields and including spaces in the delimiters box, but this results in unwanted behavior.



  • Category Parse

If Alteryx encounters an error in a RegEx tool - it throws an error:

 RegEx (9) The field "Field1_Matched" is not contained in the record.


This is a somewhat confusing and misleading error message because the input data and the regex configuration have no "Field1" at all, so the error message does not assist with resolving the issue.


Could you please re-look at the error messaging on the RegExt tool to see if we can make RegEx errors easier to resolve by giving a self-descriptive error message?


Example below:

Here I was trying to tokenize by using the . to represent any character - however Alteryx is struggling with this.

Annotation 2019-05-20 223352.png

Hi there,
In working with dates in strings, we have an option to use the DateTime tool to convert from string to DateTime, or to use a formula with DateTimeParse.
The DateTime tool is limited in the number of formats possible - and even if you edit the XML directly, you often can't get exactly the format that you are looking for (e.g. 01-sep-1975 - dd/mmm/yyyy) because it's not in the predefined list of "Format of Input String".
The DateTimeParse is similarly painful because it requires you to go and look up a set of arcane %b or %y characters on the Alteryx Help screen.
Would it be possible to change the treatment of dates so that:
- DateTime tool can take any format that you need - and includes a simple format builder tool so that people don't need to remember the codes
- The DateTimeParse function also uses the same format codes as the DateTime tool, and also includes a simple formula/format builder so that people don't need to remember the codes.
- When you point a DateTime tool to a column in a data-stream - it can read the data to determine the best format to suggest
- Finally - if you could profile the data, and clean it up visually (like the new release of Tableau; or like Cognos) where you can see the values on screen and apply a transformation to them in-situ, which then translates into Alteryx Formulas - it would be even more useful and rapid.
Cleaning up date handling would speed up date processing tremendously. 

  • Category Parse

We frequently report on our data by week. However, the DateTimeTrim function (in the Formula Tool and others) does not support this trim type.


Some workarounds have been posted that involve calculating the day of the week and then subtracting it out:


It would be very helpful to update DateTimeTrim as follows:


  • Add a <trim type> of 'week' 
  • Add an optional parameter for <start of week>
    • Default value: 0 (Week beginning Sunday)
    • Other values: 1 (Week beginning Monday), 2 (Week beginning Tuesday), etc.




  • Category Parse
Top Liked Authors