Alteryx Designer Desktop Ideas

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

In some cases, the information about incoming columns to tools are (temporarily) forgotten, e.g. if Autoconfig is switched off, if the incoming connection is temporarily missing, or if column names are generated dynamically and the workflow has not been executed, yet.

Many tools deal with that situation well, e.g. Selection, Formula, or Summarize. In these cases, the tools tell the user that they cannot find incoming columns, but they preserve the configuration so that the user still can (at least partially) work on these tools and important information on the configuration is not lost:

Example Select Tool

1. First step: Connections present, configuration typed in:
   
2. Second step: Connection cut, confguration opened. The configuration looks screwed up but implicitly contains all settings:
   
3. Third step: Connection re-connected. The configuration is as before:
   

Other tools behave the opposite, for example Unique or Macro Input (an for sure many other tools). If the incoming columns are currently unknown to the Designer and you click once on the symbol, the entire configuration of this tool is lost. You might try to get the configuration back by pressing undo. This, in most cases does not work. Or, even worse, you find out what happened later when it's too late for undo. In this case, you either have an old version of that workflow to look up the configuration or you have to re-develop it. In any case, this is unnecessary and time-consuming software behaviour.

Example Unique Tool

1. Step 1: Connections present, configuration typed in:
    
2. Step 2: Connection cut, confguration opened. The configuration is empty:
   
3. Step 3: Connection re-connected: The entire configuration is permanently lost:
   

I wasn't sure whether I should report this as a bug or a feature enhancement. It is somehow in between. Two aspects tell me that this should be changed:

• Inconsistent behaviour of different tools for now reason,
• Easy loss of programming work, resulting in time-consuming bug fixing.

Please make sure that all tools preserve their configuration also if information on incoming columns is temporarily lost.

I noticed the Workflow appears to validate the SQL when you click on the three dots next to the SQL statement in the Workflow Design.  My suggestion is to not run the validation until after the workflow is saved.

Hello all,

I'm currently learning Pythin language and there is this cool feature : you can multiply a string

Pretty cool, no? I would like the same syntax to work for Tableau.

Best regards,

Simon

• Have anyone experienced the same error?
• If yes, is there any workaround to connect with M365?

Not sure I'd call this a user setting, but I couldn't figure out the right heading this belongs to. 

When opening files, there are often times a couple of files at that aren't run on any kind of schedule or set time frame but you come back to when you need to run them.  

There should be a way to set "FAVORITES" for a handful of files that you find yourself referring to on a repeated basis, but too far back to be on the 'recents' list because you open too many other files. 

Hello,

As of today if you want to connect to Snowflake or MongoDB, you have to overwrite the default LUA Files, and that requires admin rights. I don't see the point of not including the good LUA files directly in the Alteryx packaging.

Best regards,

Simon

I would like to see Designer offer me the ability to chain workflows together where once Workflow A completes, Workflow B will automatically start.  There are times when linear processing is required in order to avoid dependency issues and/or for making it easier to organize complex processes. It would require outputting results to static files and it would take longer to process than the standard approach, but that is an expected trade-off.  Offering a GUI drag-drop "orchestrator" to tell Designer the order of operation would be even better than having to manually open each workflow and tell it which workflow to kick off next.

Hello

Cartesian product is a common issue when joining dataset with a bad key. What I suggest is an option to check if there will be a cartesian product on the join tool.

-there is a label "Cartesian product (non join key uniqueness) detection"
-under it a drop down menu with three choices
-do nothing
-fail
-warning

Algo :
if do nothing==> well... do nothing more than actual behaviour.
if "fail" or "warning" : count distinct of join key versus count row on each side of the join. If none is unique, display a warning or an error message.

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.

The Formula Tool does a good job of autocompleting expressions (for example an open square bracket will show you variables in your dataset), as well as syntax highlighting (coloring variables, keywords, strings, etc).

I propose having this feature available in all tools that use the expression editor, particularly common ones such as the Multi-Row Formula Tool and the Multi-Field Formula Tool.

This parity across tools would provide a more consistent experience for the user and increase one's productivity using these tools. It's incredibly helpful for beginners and seasoned Alteryx users alike and should be available wherever possible.

Issue

Whenever a Summarize tool is used, it renames the output field (e.g., sales becomes SUM_sales or AVG_sales).  

Proposal

I think a reasonable compromise is to by default not rename fields in the Summarize Tool, but to include an option (in the tool, or in global settings) to allow for renaming.

Rationale

I have yet to come across a use case where automatic renaming of aggregated fields is desirable. What I have come across is the annoyance to rename the fields back to what they were with a Dynamic Rename tool, and sometimes having to do this multiple times (e.g., converting back a SUM_SUM_SUM_sales back to sales). Additionally, automatic field renaming causes workflow errors when workflows are later modified by adding/removing a Summarize tool (e.g., if you later add a Summarize tool, all downstream steps will expect the "sales" field and not know to use the "Sum_sales field). 

Automatic Renaming feels very much like historic Excel with Pivot Tables field renaming and not reflective of modern code-based workflow best practices.

I appreciate you considering this improvement.

Similar to this idea, I think it would be really helpful to be able to search for fields in the dropdowns when using the Sort tool. Having to scroll through all of the possible field names can be a chore if you have 50+

Today, there is an checkbox to "Disable All Tools that Write Output" within the Runtime settings for a workflow.  Setting this option requires at least 3 clicks:

• Click on the canvas
• Click the "Runtime" tab in the Configuration pane
• Click the checkbox

Could a keyboard shortcut be added for this?  I've spoken to several users who leverage this feature and, while it is already a time saver, it seems helpful enough where a keyboard shortcut is warranted.

Whenever I overwrite an Excel sheet with data of the same format just different values (e.g. Q2 data versus Q1 data) all of my Pivot Tables break and I have to manually recreate them even though the schema didn't change.  Somehow the Table is being deleted/removed and replaced with a completely different Table which is what causes the Pivot Tables to break.  The only way to avoid this is to manually set the Cell Range, but who has time for that?  The only solution I have found is to manually copy all values and paste them over the existing data which is very inefficient the more sheets you are working with.

Hello,

Just like Monetdb or Vertica, Clickhouse is a column-store database, claiming to be the fastest in the world. It's available on Cloud (like Snowflake), linux and macos (and here for free, it's open-source). it's also very well ranked in analytics database https://db-engines.com/en/system/ClickHouse and it would be a good differenciator with competitors.

https://clickhouse.com/

it has became more popular than Greenplum that is supported : (black snowflake, red greenplum, orange clickhouse)

Best regards,

Simon

I sometimes have to swap (change the order of) two tools in a flow. It is a bothersome task, especially when there are many connections around them. I would like to suggest two new features for such a situation. It would help if either could be realized.

Swap tools

Select two tools, right-click, and select "Swap" option. 

Move and connect around

Drag a tool holding down Alt key (or something) to move it from the stream and connect around. After that, we can drag and drop the tool to the right place.

Hello all,

According to wikipedia https://en.wikipedia.org/wiki/Materialized_view

 In computing, a materialized view is a database object that contains the results of a query. For example, it may be a local copy of data located remotely, or may be a subset of the rows and/or columns of a table or join result, or may be a summary using an aggregate function.

The process of setting up a materialized view is sometimes called materialization.[1] This is a form of caching the results of a query, similar to memoization of the value of a function in functional languages, and it is sometimes described as a form of precomputation.[2][3] As with other forms of precomputation, database users typically use materialized views for performance reasons, i.e. as a form of optimization.

So, I would like to create that in Alteryx, for obvious performance reasons in some use cases.

This is not a duplicate of https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/In-DB-Create-View/idi-p/157886

Best regards,

Simon