Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the like in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature

Suggest an idea

As detailed in How-To-Create-an-Optional-Field-for-an-Analytic-App, when using the "Generate Field Map for Input Data Tool" option in the File Browse tool, you can easily specify a field as "optional" by adding "(Optional)" to the field name in the input template. However, when you do this, it no longer automatically matches field names in the selected file unless those field names also include "(Optional)" in the field name. It would be very helpful to the user experience if the tool matched the name of the field prior to the "(Optional)" text with the fields in the selected file.


For example, if you include the field "Address (Optional)" in the input template file, and you select a file which has a field named "Address," that field is not automatically selected as a matching field. The user must manually match that field. "Address (Optional)" should automatically match "Address" if it exists. But, of course, if it does not exist, it would not match and it would remain optional.



In the Output Data tool, when the file type is YXDB, one of the options is to Save Source & Description.


Splitting these into "Save Source" and "Save Description" -- independent options -- would be useful.


Sometimes I don't want the file recipient to know how a field was derived but I want to include a description.


Right now there is no easy way of doing this.


It was great to find the DateTimeTrim function when trying to identify future periods in my data set.


It would be even better if in addition to the "firstofmonth" , "lastofmonth" there could be "firstofyear", "lastofyear" functionality that would find for instance Jan, 1 xxxx plus one second and Jan, 1 xxxx minus one second. (Dec, 31 xxxx 12:58:59) respectively.


I'm not sure if time down to the second would even be needed but down to the day period.







I recently started to take online trainings on Alteryx and came across Tile Tool. Though could understand the purpose to some extent, it would be great if the tool is explained in more depth along with more examples and also how the tile number is calculated for the examples.





Occasionally, the Calgary Loader tool will not write out all fields passed to it.  This seems to happen after writing out a certain number of fields then later, when rerunning, adding a new output field.  Very annoying because you don't know it will happen until processing is complete and you examine the result.  I usually manually delete the calgary files prior to rerunning, to avoid the versioning, but it still happens.


Also, please make the versioning optional with a check box, default off.




I work with alteryx databases a lot to store some historical data so I don't have to pull it in the future. It would be great if there was a way when creating the database, where I could lock them for editing and can only be edited by select usernames and passwords.





Hope this is fairly self-explanatory.

I'd like to be able to create presets for Summarize tool.  Instead of having Group By, Sum, Count, Count Non Null, etc on top of the libraries of functions, put them into their own category.  Users could then create a Favorites and the functions that they use the most would be stored in that section (editable by user).


Hi All,


I believe the following would help improve the functionality of Select Tool.


The idea is to have a defaulting option for each of the field in the Select Tool (which I believe should be a light weight Tool i.e. not adversely impacting performance and gives best exhaustive picture of all columns flowing through a (/particular point in ) pipeline).


Following are some of the cases where defaulting might come handy -


1) Fields which are supposed to hold monetary data - instead of Null, one can put 0.00 to help roll up summary properly.
2) Fields which are supposed to hold dates (say expiry date) - instead of Null, one can put some enterprise standards like 31-12-2099 to avoid mixing Nulls and 31-12-2099.
3) Fields which are supposed to hold purchase quantity/number of employees/number of merchandise - instead of Null, one can put 0 (and not 0.00) again to help with roll up summary.
4) Fields which are supposed to hold Currency - instead of Null, one can put USD.
5) Fields which are supposed to hold dates (say this time create date) - instead of Null, one can hardcode actual date, or an additional feature to put Now() kind of functions.


At present one of the options of achieving same might be to put a Formula Tool and to code whatever is desired inside the Formula Tool.


Benefits of having the functionality inside Select Tool would be -


1) It would be more user friendly and call for faster build to just write '0.00' or 'USD' or '31-12-2099' as compared to writing IF IsNull()... statements.
2) Inside Formula Tool, user needs to pull desired fields from the drop down and hence exhaustive view of all fields passing through pipeline is not available.

Pain in selection of fields from drop down and writing actual formulas might be aggravated with the number of columns increasing and might be more prone to human omission related errors.


Rohit Bajaj


Hi All,


It would be a given wherein IT would have invested effort and time building workflows and other components using some of the tools which became deprecated with the latest versions.


It is good to have the deprecated versions still available to make the code backward compatible, but at the same time there should be some option where in a deprecated tool can be promoted to the new tool available without impacting the code.


Following are the benefits of this approach -


1) IT team can leverage the benefits of the new tool over existing and deprecated tools. For e.g. in my case I am using Salesforce connectors extensibly, I believe in contrast to the existing ones the new ones are using Bulk API and hence are relatively much faster.

2) It will save IT from reconfiguring/recoding the existing code and would save them considerable time.


3) As the tool keeps forward moving in its journey, it might help and make more sense to actually remove some of the deprecated tool versions (i.e. I believe it would not be the plan to have say 5 working set of Salesforce Input connectors - including deprecated ones). With this approach in place I think IT would be comfortable with removal of deprecated connectors, as they would have the promote option without impacting exsiting code - so it would ideally take minimal change time.


In addition, if it is felt that with new tools some configurations has changed (should ideally be minor), those can be published and as part of
promotions IT can be given the option to configure it.



Rohit Bajaj


If you copy a text box named ClientCode to another workflow, the name of the box will be reset to text box(#) in that new workflow. That can be a snag if the workflow the text box is contained in is deployed to gallery as an app that is ran via the gallery API... the API parameters will be looking for a text box named ClientCode but is now named text box(#). This happens almost in the background without the developer knowing they have renamed the text box and the ES eventually failing. This can be annoying; it would be great if the name were inhereted. 


If you copy a text box named ClientCode to another workflow, the name of the box will be reset to text box(#) in that new workflow. That can be a snag if the workflow the text box is contained in is deployed to gallery as an app that is ran via the gallery API... the API parameters will be looking for a text box named ClientCode but is now named text box(#). This happens almost in the background without the developer knowing they have renamed the text box and the ES eventually failing. This can be annoying; it would be great if the name were inhereted. 


During development it seems the syntax checker or whatever process runs behind the scenes after a tool is modified reviews the full workflow. 

Ex - Just from observation if I modify the file name in an output tool I don't see why it would rerun the full syntax check process.


This reduce the time waiting to continue development.


It would be great if we could make use of HTML5, in the same way the new formula tool will, by enabling autocomplete in all relevant tools - Filter, Multi-Row/Multi-Field Formula etc...



When using horizontal layout the status messages can overlap those of other tools meaning % progress can't be read:


Overlap Alteryx.png

Status labels would be better placed above the tools, not to the right.


Hi all,


I often feel like workflows can easily become overly cluttered with Browses, especially around Join and other multi-output tools. I need to see the output of most of the data streams, so I can't necessarily just delete the Browses and be done with them (as I'll like need to see them over and over again).


To solve this problem, Alteryx could potentially add a "nested browse" view or tool. I've attached a picture to show what I mean. This would unclutter the area right after multi-output tools significantly.


What are your thoughts? Have I missed any neat trick or functionality that can already do something like this?



Nested Browse View Sketch.png


Sometimes when I'm working on a workflow a connection string between two tools will take a path that either causes the workflow to become more cluttered or overlaps another tool etc. I usually format these strings to be wireless but if I am presenting my workflow to someone who is unfamiliar with Alteryx, wireless connections can cause much confusion. It would be great if I could determine the path a connection string takes, much the same way you can draw/manipulate a line in ppt or word (i.e. if the string could have nodes that could be dragged around tools, containers, etc.)




When you use a Find Replace tool, it would be GREAT if you had a select all option for what you want to append to the find data set.


It would be extra GREAT if you added the ability to draw a box over the ones you want to add, or have a feature where you could select the first on on the list and hold the shift+ctr to select multiple lines at once.




I would love to see the ability to have a hyperlink (or even more formatting options) in my app output message. 


Currently I when I have an app that runs and I want my users to move off to a different web location they have to copy and paste the url that I have rather than just clicking a link and going to the external report.


Have been using Alteryx GA component and found some issues, apart from the setup teething problems I was having.

So thought I’d let you know , in case it’s just not me who is suffering…


We do a fair amount of marketing for our Private business and like to measure conversion of the pipeline.

I’ve been looking at Lead -> Account -> Trade

Have been drilling into lead data with little source identifiers which are appearing in a NULL bucket..


When using Alteryx

I noticed that the Profiles for my id do not appear fully in Alteryx via the drop down..

It picks up QA profile data instead of the live profiles and does not show the whole set ?

Tableau works correctly showing the complete set of GA profiles

I don’t have the full set of profiles…


Maybe config related but why bring in some profiles and not others when I can access fine from GA directly and via Tableau ?


Trying to set these profiles and config files seemed problematic – reset to default removes the 4 config files, when you run again it doesn’t create them.


Had to keep a copy of these and put them back in manually or cpy an old widget and run a new one up from that …


Resetting the profile and saving caused other errors to appear related to the Tokens…


Found that annoying and a waste of time… immature (arghh) !


I think the Alteryx implementation is immature and not as good as Tableau and you have more work to do…! But may just be me !


Can you help improve it as I’d like to pull and blend reliably via Alteryx and do this for a range of dates to avoid sampling data


I do love the product but love this a little less than anything else …


I’d also love to be able to pull from Tableau data sources into Alteryx as we have all of our history in Tableau server

Has anyone else wanted the same ?

Obviously you can store to TDE but want the reverse… to pull from Tableau server





You know how when you pull a new tool onto a canvas where you already have a workflow it wants to auto connect to the closest tool where it lands? While this can be useful it causes major issues when it moves the entire workflow you had in place. What makes this more frustrating is when it does this and you can't undo everything it did. Sometimes I spenda lot of of time fixing what it messed up. On top of which the tool it connected too was wrong!


Like I said it can be useful, but the adjustment of the entire workflow is HIGHLY unneccesary.


Could you PLEASE adjust this feature to auto connect without moving the entire module?!


Thank you 🙂

Top Liked Authors