Alteryx Designer Desktop Ideas

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

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

Submission Guidelines

Featured Ideas

0 Likes

It would be very helpful to have a find and replace work in duplicated formula.  especially if it is long.

  • Enhancement
0 Likes

Hi,

 

I was thinking that this might be nice addition - while Joining two inputs at the bottom there is always possibility to check if we want to include Unknown columns. Maybe we could specify if we want to join Unknown columns only from Right Input or Unknown only from Left Input. I know I would use this in my workflows. 

 

Thanks

Alicja

I think we can all agree that Workflow Summary Tool is immensely powerful in summarizing large and/or complicated workflows.  However, some companies have begun to bar the use of certain GenAI applications, like ChatGPT. Unfortunately this makes the use of the Workflow Summary Tool impossible.  At the same time those companies are allowing the use of other forms of GenAI, like AzureAI.

 

In the Workflow Summary tool, it would be nice to have the capability to select which GenAI engine you want to use (ChatGPT, AzureAI, etc) so that you don't break corporate policy by using barred applications.  This could simply be a dropdown in the GUI configuration for the Workflow Summary Tool with a list of the most common engines.  The user would then supply their API key for that engine, and you're off to the races.

  • Enhancement

Hi

 

The action of the 'tab' key in configuration window recently appears to have changed from indenting to a navigation function. 

 

The user should be able to select which action the tab key performs. 

 

Alternatively, tab should indent and shift-tab (or alternative) navigate. I'm not the only one who would appreciate the choice.

 

PuffinPanic

 

Would be nice to have a way to cache-uncache all inputs or a selected group of tools.  Caching and Uncaching workflows with many input tools or slow data-read tools gets to be a bit cumbersome.  Would be a nice QoL improvement :)

 

I looked around for something like this but didn't see a solution, so thought I'd recommend.  Please let me know if something like this exists already natively in designer desktop.

  • Enhancement

If you cancel a workflow while its writing into a file, the file creation will not be rollbacked and hence a partial file would have been created.

This is problematic when working with incremental load relying on file from the past.

 
My proposal is to have an output mode which allow transactionnal writing. If workflow is cancelled nothing is being written. This could be done by writing first in a temporary file before renaming it. 

Hello All,

 

I'm using the dynamic input tool for SQL requests in my Workflow (WF).

I'm using the "Replace a Specific String" to replace elements in the SQL statement dynamically depeding on results of prevoius tools, user input etc.

So the statement looks like

select * from Schema_Name_xx where invoice_number = 'invoice_number_xx'

 

Since Schema_Name_xx is no valid Schema in the Database, the statement (= Validation) won't work. Only if I replace Schema_Name_xx by e.g. Invoice_Data_Current it will work, same with the invoice number, invoice_number_xx is replaced by e.g. 4711.

Therefore, validation makes no sense and will never work, only if the WF is running, the correct Schema is inserted in the SQL statement by the "Replace a Specific String" function.

It would be great to disable it in the users settings or wherever in the Designer, changing a config file would also be great :-)

Pls. note: I'm thinking (since I'm not allowed anyway ;-)) about changing/disabeling anything in the Alteryx Server settings.

 

Reason:

1. Speed: Validating a WF with SQL statements that don't work takes time (every time I save it), sometimes I get even a timeout...

2. WF error entries: Each upload with a  failed validation creates an entry in the WF result list which makes it harder to seperate them from the "real" WF errors...

 

Thanks & Best Regards,

Thomas

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:
    select-step1-configuration_entered.png
  2. Second step: Connection cut, confguration opened. The configuration looks screwed up but implicitly contains all settings:
    select-step2-incoming_connection_missing.png
  3. Third step: Connection re-connected. The configuration is as before:
    select-step3-incoming_connection_present.png

 

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:
     unique-step1-configuration_entered.png
  2. Step 2: Connection cut, confguration opened. The configuration is empty:
    unique-step2-incoming_connection_missing.png
  3. Step 3: Connection re-connected: The entire configuration is permanently lost:
    unique-step3-incoming_connection_present.png

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.

  • Enhancement

Containers are a great feature.  They allow us to create larger workflows in smaller canvases, and manage the flow and appearance of our work.  However the design whether intentional or flawed that allows the container window to interact with the layers behind it is annoying.  Connection wires should not redirect within a container because of things on the canvas behind the container.  Likewise if I have a container open, I should not be able to grab a tool or container behind the open container through the container canvas.  Please fix this flaw.

  • Enhancement
0 Likes

Hello, I believe this feature will be useful for many people.
The idea is to select multiple instances of the same tool and the configuration that we set will be applied to all the selected tools. Furthermore, it will be useful to be an easy way to select all instances of the same tool across a workflow with a shortcut in order to edit them more easily.

  • Enhancement
0 Likes

I am suggesting an addition to the Auto Field Tool.  Create an option that allows only auto sizing of the fields and does not change the field type.  A check box that says Auto Size Only.  The tool would recognize any fields that can be resized based on their incoming data field type and will not change the data type.  The resizing function is very helpful to maximize workflow performance, but I currently do not use it much because it guesses wrong on the data types.  This causes problems also when data inputs change.  Whereas setting to auto size only, it can streamline the data but let the user be confident the data types would not change. 

 

Thank You

To embed the "Not ok" filter option in the browse tool

 

Not ok.png

0 Likes

As of version 2023.1 once a workflow is locked, it cannot be unlocked. If Alteryx can unlock it, can it be made into a user option?

 

My idea has two parts. See the images for examples.

1. Add an option on the lock screen so the user can get an unlock passkey.

Passkey is either generated by Alteryx or set by user

 

2. Change the behavior when trying to open a locked file by giving the user an option to enter the unlock passkey.

Same behavior if there is no passkey

Dialog box with passkey input and cancel button if a passkey exists

 

This would be useful as a way to revise or edit a workflow or update the expiration date on the existing workflow without having to reload or resave a new file.

 

modified lock screen.png

 

Unlock workflow.png

Dynamic macros that fetch the current version at every run time vs storing a static copy of the macro with the workflow at publish time are challenging to pull off using shared drives. 

 

This suggestion is to store dynamic macros in the gallery and secure their use with collections.

 

Changing the Macro Input tool in an existing macro is dangerous and can result in unmapped fields or lost connections in workflows using the macro. For example, we have a widely used macro for which we'd like to change the name of an input field, change it's default type from Date to DateTime, make it optional while keeping other fields mandatory. Currently, we cannot find a solution which would not require us to fix each workflow using the macro after changing it. We should be able to change the field names, field types (e.g. String to V_WString, Date to DateTime), select optional fields and do other modifications to Macro Input without having to update each workflow using the macro. The new Macro Input UI could be enhanced with a window similar to that of Select tool's. Technically, the Macro Input fields could have a unique ID by which they would be recognised in workflows, so the field names would just be aliases that could be changed without losing the mapping. In summary, we are restricted to our initial setup of Macro Input and it is very complicated to change it afterwards, especially if the macro is used widely.

Right click + "Insert After" and Right click + "Paste After" should behave the same. In the picture below I show the two cases. Currently, the "Insert After" option inserts a tool between the selected tool and the tools after it. The "Paste After" creates a new branch with the pasted tool. I think the "Paste After" should behave the same as the "Insert After": paste the tool on the existing branches. In case we want to create a new branch, we will paste the tool and connect a new branch to it.

1.PNG

  • Enhancement

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.

  • Enhancement

Quite often, I would love to be able to use Browse tools already while the workflow is still running, if that specific Browse tool has completed (green box around). This would help to debug and save a lot of time.

haraldharders_0-1686727471952.png

In this case, the lower Browse tool would be enabled already now.

 

In the RecordID tool,  provide additional options for the creation of the ID, specifically allow for the ID to 'Intervals'. 

For example, Record ID every 10, meaning instead of creating an ID of 1, 2, 3, 4, 5 .... you could create an interval of your choosing, the most obvious would by 10 or 100  thus your ID's would then be 10, 20, 30, 40 ....  or  100, 200, 300, 400, 500 ... etc. 

 

 

0 Likes

After closing the Table or Query option on an Input Data tool, the table layout in the Visual Query Builder view gets reset to stacking the tables/views on top of each other. It would be great if the layout stayed the way I left it the last time I closed it.

IdeaIdea

 

CurrentlyCurrently

Top Liked Authors