Alteryx Designer Desktop Ideas

Anytime you create a formula in the formula tool, you get a data preview based on the values in the first row of data.  However, if you have a complex "IF c THEN t ELSEIF c2 THEN t2 ELSE f ENDIF" formula then the data combination that gives a TRUE result will likely exist on another row.  Therefore, you need to run the workflow, or place a filter tool upstream to isolate the specific row, to test if the formula result is correct.  

It would be easier if you could select the Input anchor of the Formula tool, then filter the data in the results window to isolate the row in questions, then the data preview would be based on that filtered data set.  I believe this would save a lot of time in the workflow development phase.

So many tools especially Spatial Tools require a browse tool to be useful. Why not automatically add a browse tool when you add a spatial tool it could even be an option you could select. "Yes Auto Add browse" or not. Even during spatial trainings the instructions keep saying add spatial tool now add a browse tool and hit run. we can always toggle of the browse tools or delete them once we are finished developing. i know there are keyboard shortcuts and i use those but i think this would be a very simple addition.  

Hello,

I really would appreciate the ability to store our templates in a Teams/Sharepoint (or whatever exists) folder. However, it doesn't work today :

Best regards,

Simon

when using switch formula as a more elegant way then if else

't' is not working in switch while it working in if then.

so i recommend to have a formula call True() and False() as excel to solve this issue. 

At a minimum one checkbox added to the Summarize tool, which would trigger the output to be automatically sorted in the order in which the fields were aggregated.

On a more elaborate level, it could allow the user to select a different sort order than that in which the fields were aggregated.

Currently the summarize tool field selector has one empty column on the left side that must be clicked on when selecting the fields, otherwise the 'Add' button does not activate.

I don't understand why the need for this empty column to be used when selecting the fields to aggregate/calculate.  Why can't we select the fields by clicking directly on the names of the fields instead?  Selecting fields this way is actually possible, but then the 'Add' button does not allow for the selection of the 'Group by' or aggregation method.

This creates confusion, especially for beginner users who might click on the field names, see them selected and be puzzled why the 'Add' button is not working.

Thanks!

sometimes we deal with hundreds of columns and it's hard to scroll and locate a specific one in the Data panel.

In the Metadata panel it's easier to locate the fields by scrolling vertically, however it would be even easier if we could click on the 'Name' column header and have that temporarily sorted so as to quickly locate a given column.  (This would be IDEA 1).

Additionally, but not necessarily dependent on IDEA1, if we could have the Record number of each of the fields in the metadata, also included alongside their respective names in the Data panel, that would make it for much easier location of particular fields in the Data panel, as users could look for a given field in the Metadata, find their 'order number' and then switch back to the Data panel and scroll directly to that number.

Additionally, column name search buttons could also be added to both Data/Metdata panels for a 'contains' like field name search.

Thanks!

The Unique tool is likely lighter than the Summarize tool and extremely useful to identify and remove duplicates, however unlike the JOIN tool where one can select which fields are included in the output, the unique tool will return all fields regardless.

It would be extremely useful if the UNIQUE tool also featured a list of fields to be included or not in the output for users to select from, because many times, all we are trying to extract is the list of unique values from a given column in the dataset and the other fields are not needed, neither do they make sense in this particular type of operation.

Thanks!

Dynamic Input should either:

(a) have the option of merging files with different field schemas

(b) Return a list of rejected filepaths

One of the problems I have with using Alteryx is the frequent need to input a bunch of files, but a few have an extra/missing field. The extra/missing field is often unimportant to me, but it means that the dynamic input doesn't work.

Work on allowing workflows to run successfully as the same way as the Designer.

1.  Allow use of DCM connections in Workflow.

2.  Allow use of AMP engine in connections.

3.  Expose the full execution log in the Scheduler Output Window.

4.  Refresh the screen when a Schedule is running frequently showing the same detail as in the Execution Log.  

5.  Allow a retry options for Scheduler.  Allow for number of retries when an Inteval between retries similar to SQL Server Job Agent or other schedulers.  

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,

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

*unknown field is not available in the interface list box when it connected to a macro input.

i wish it has the "*unknown" field like in the select tool.
because it normal that the data flow has new columns and need the macro to take care the new columns. 

for iterative macro, generally it had 2 anchors, one if it is for iterative, and it normally no output (whether got error or not)

it good to have option to remove this anchor when using it in workflow. 

so other user no need to identify which one is the True output and which one is just iteration.

additional, if this can apply to input anchor.
(i just built one macro where i don't need the start input, but the input need to be iterate input)

Hello,

As of today, there are only few packages that are embedded with Alteryx Python tool. However :
1/Python becomes more and more popular. We will use this tool intensively in the next years
2/Python is based on existing packages. This is the force of the language
3/On Alteryx, adding a package is not that easy : you need to have admin rights and if you want your colleagues to open your workflow, it also means that he has to install it himself. In corporate environments, it means loosing time, several days on a project.

Personnaly, I would Polars, DuckDB.. that are way faster than Panda.

Hello,

There are several dozens of data sources... maybe it would be useful to have a search in it?

Best regards,

Simon

(1) The green banner saying that the workflow has finished running should stay until dismissed

(2) The indicator on the tabs showing which workflows had run should be colour coded (still running / completed without errors / completed with errors)

Thanks!

The Email tool does not send out e-mails after an error occurred in the workflow. Since this usually is a good thing, it sometimes would be helpful being able to send out e-mails also in case of errors.

In particular, I want to send out an e-mail with a detailed and formatted custom error message.

Thus, please add a check box "Also send mail in case of errors" which is off by default.

Side note: The Event "Send mail After Run With Errors" does not work for me because it is too inflexible. Just sending out the OutputLog is not helpful because the error message might be hidden after hundreds of rows.

Hello,

A lot of tools that use R Macro (and not only preductive) are clearly outdated in several terms :
1/the R package
2/the presentation of the macro
3/the tools used

E.g. : the MB_Inspect

Ugly but wait there is more :

Also ; the UI doesn't help that much with field types.

Best regards,

Simon