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

The "Manage Data Connections" tool is fantastic to save credentials alongside the connection without having to worry when you save the workflow that you've embedded a password. 


Imagine if - there were a similar utility to handle credentials/environment variables. 


  • I could create an entry, give it a description, a username, and an encrypted password stored in my options, then refer to that for configurations/values throughout my workflows. 
    • Tableau credentials in the publish to tableau macro
    • Sharepoint Credentials in the sharepoint list connector
  • When my password changes I only have to change it in one place
  • If I handoff the workflow to another user I don't have to worry about scanning the xml to make sure I'm not passing them my password
  • When a user opens my workflow that doesn't have a corresponding entry in their credentials manager they would be prompted using my description to add it.
  • Entries could be exported and shared as well (with passwords scrubbed)

Example Entry Tableau:

AliasTableau Prod
DescriptionTableau Production Server

Then when configuring a tool you could put in something like [Tableau Prod].[Password] and it would read in the value.


Or maybe for Sharepoint:


DescriptionTeam sharepoint location


Or perhaps for a team file location:

DescriptionRoot directory for team files


Any of these values could be referenced in tool configurations, formulas, macro inputs by specifying the Alias and field.

1-3-2019 12-43-52 PM.png


Well, the title is pretty simple : it appears that the tendancy right now is to  have web version of any software on a server.

A few notes about that :
-a lot of Alteryx competitors are already in this mode and it's hard to sell you're still with a desktop-only mode for design, even if the product is far better.
-a good idea is the one used by Qlik with Qlik Sense : they still have a desktop and a web version of Sense but the desktop works mainly as an hidden browser plus an engine. The web version is cool too because you can make your own application, or your own data connection etc..
-the main interest of a web implementation of Alteryx would be to reduce installation on client computers (and that means packaging the installer, managing the data connection, the paths, the access to macros... etc) and to have a better control of the users.

PS : this idea is soooo simple and so obvious I'm surprised I didn't find it. It may be a duplicate.

So far, Alteryx Products are offered in 6 different languages, which is a great thing indeed !!


However there is a lack of a toggle option to effortlessly switch the interface to a different language.


As a standard feature users should be allowed to switch language without re-installing the product (applicable to all Alteryx products)



I would like to have all my annotations show on top of the tools by default. I can change them one at a time, but I would like to be able to change the default setting to be "Show Annotations on the Top" always.



we have several environment in our organization : dev, recept, production.


In order to make that change safe we intend to make several connection (standard alias)  like






In our workflows, we want to use aka:%Question.v_environment%HIVE


Sadly, this solution does not work despite the value defaut. 



It would be useful if enhancements could be made to the Sharepoint Input tool to support SSO. In my organisation we host a lot of collaborative work on SharePoints protected by ADFS authentication and directly pulling data from them is not supported with the SharePoint input tool, it is blocked. The addition of this feature to enable it to recognise logins would be very useful.

  • Environment

Please allow the "Manage Data Connections" window to resize ... including changing the widths of the Columns (Name, Connection Summary, Type).



ps. There may be other windows that may need to have resizing added to them ... it never hurts.


Please extend the Workflow Dependencies functionality to include dependencies of used macros in the worflow too. Currenctly macros are simply marked as dependencies by themselves, but the underlying dependencies (e.g. data sources) of these macros are not included.


We have a large ETL process developed with Alteryx that applies several layers of custom and complex macros and several data sources referenced using aliases. Currently the process is deployed locally (non-server) and executed ad-hoc, but will be moved to the server platform at some point. 


Recently I had to prep an employee for running the process. This requires creating aliases and associated connections and making sure that access to needed network locations is in place (storing macros, temp files, etc.). Hence I needed to identify all aliases and components/macros used. As everything is wrapped nicely by a single workflow, I hoped that the workflow dependencies functionality would cover dependencies in the macro nodes within, but unfortunately it didn't and I had to look through the dependencies of 10-15 macros.

In order to perform audit-trail logging - it would be valuable to have 2 new capabilities


a) environment variables which show the workflow name; filepath; version; run start date and time; etc.   For any worklows we build, we need to have a solid audit trail to be SOX compliant, so having this detail available as a data field to write and manipulate is essential

b) A logging component.   What would be great is a component that you can drop on a workflow, not connected to anything, which is able to trap the start; end; runtime; version; etc of a workflow; and commit this to any output data format (CSV or ODBC etc).   This logging tool would need to be able to capture the full runtime, so it would need to be the last thing that runs (which means it may need to exist in parallel to the main workflow in some way).    This is not currently possible with a complex workflow with outputs, because it's not possible to identify when the entire workflow ended; or the runtime (since output tools don't have an onward connector to pass flow-of-control to catch the final end-time)


Again, both of these are necessary to meet audit requirements for workflows and prodcution-quality ETLs for BI data warehouses.

Hi all,

I was wondering if any of you have achieved "Transaction rollback" type of feature in alteryx.


Following is the usecase:

If a workflow that writes data into multiple outputs (could be relational tables / files) is failed half way through in writing to one of the outputs, is there an option to rollback the partially loaded data & reset the process to the original state (i.e., before the execution of the workflow)? (OR) does this needs to be done programatically?


There is a workflow level property - "Cancel Running Workflow on Error". This stops the execution but doesn't perform rollback.




Many times; ideas for new ways to use Alteryx come to me while I'm not at work.

Most of the time that happens, I can use RDP via VPN to get to my work desktop.

But sometimes it isn't easy to do that.  Like when I'm driving, outside for a run, in the shower.. you get the idea.


My point is that there should be a mobile app for Designer (iPads and Android tablets).  The mobile app wouldn't necessarily need to be connected to the actual sources live (maybe require a template used for input for ODBC; but allow connections to HTTP/FTP/local sources). 

The user would design the workflow, and then have the option to email the schema to themselves (or others) so that once back at work, one could pick up where they left off.


Although I would prefer to use it on an iPad, it could technically be used on an iPhone as well.

For an example of how that could look, see the iOS app "Workflow".  That, in combination with the now defunct "Schemes" was a great way to do visual programming similar to what we do in Alteryx.


I've been using Events a fair bit recently to run batches through cmd.exe and to call Alteryx modules.

Unfortunately, the default is that the events are named by when the action occurs and what is entered in the Command line.

When you've got multiple events, this can become a problem -- see below:




It would be great if there was the ability to assign custom names to each event.

It looks like I should be able do this by directly editing the YXMD -- there's a <Description> tag for each event -- but it doesn't seem to work.


If an organisation wants many Designer users to have the same macros available to them, they have to set up their own network drive to save the macros to and share that drive to all users and ensure each user has read access to it and then maps that drive to their macros. 


Instead of relying on this shared drive architecture, macro builders should be able to publish their macros to a collection in Gallery and then end users should be able to map that collection to their Macros in Designer.

It would keep the sharing of macros within the Alteryx platform and make sharing macros much more intuitive and frictionless.


Sometimes, when I am working with new data sources, it would be nice to have a dockable pane that would allow me to view the schema of all of my connected data sources. That way I could rename fields and change data types as needed without having to jump from one select tool to the other to see how the schemas compare.


I have a process that sends out about 1,500 emails. Every once in a while, it will get stuck at some Percentage and I will have to eventually cancel the workflow, figure out how many emails were sent, and then skip that many emails in order to avoid sending duplicate emails. The process of figuring out how many were sent is currently taking the % of the tool at cancellation minus 50%(since that is where it starts), Multiplying it by 2, and then multiplying that % by the number of lines to get the approximate line of data where it froze up, and then reaching out to individuals to see if they received the email to narrow down exactly where the error occurred. 


Example: 60% - 50%= 10% * 2 = 20% * 1249 = 249.8.


This has been pretty accurate in the past, but obviously is not ideal. Is there no way for it to show us how many were sent even if we cancelled the workflow mid processing of the tool?



As per this discussion, I'd like to create constants that stay with me as I create new workflows rather than creating a user constant across multiple workflows.


This could perhaps be done by editing an xml file in the bin.


It'd be nice to have Engine Constants that follow us across all workflows. Having an XML file in the bin that we can update could be a way of doing this. 


I asked this before.  WHY DO WE HAVE TO HAVE A POP UP WINDOW OPEN UP EVERY TIME WE RUN ALTERYX?!  I asked this before, and the comment was made, "there is a check box to turn it off in the settings."  Yes, that is true, there is a checkbox!  And guess what, to my surprise (insert sarcasm here), IT DOESNT WORK!  THE MOST BASIC, EASIEST THING YOU CANT GET RIGHT, and that is EXTREMELY ANNOYING.


Maybe I should send an email to alteryx to remind them I am using their product, will you feel even more important then?  Pardon that slam here in my nastygram, but this is JUST AMATEUR!


A multi billion dollar company, and youre wasting effort with this.  GEEZUZ

Top Liked Authors