Alteryx Designer Desktop Ideas

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

I have tried to search for this Idea but not located one that is same or similar. 

When searching for tools to use rather than having to click in the search bar at the top, it would be nice just to click on a blank part of the canvas and start typing for the tool that you need, then a suggest tool list pops up and you just click on the one you want to it appear. 

Thanks

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

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.

Looking for a tool to replicate the Goal seek functionality built into Excel.

Seems it could be solved by using R or iterative macros however a tool would make life much easier,

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.

When I make the workflow, the font size on Result window is no problem.

But, when we show the contents of Results window on the presentation or online meeting, the font size is too small.

I want the function which is enlarge the font size. The important point is that the current font size is okay on making workflow and the large font size is only needed on showing to the another people on presentation or online meeting.

One more point to add, it would be helpful to be able to change the font size with Ctrl + mouse wheel.

Push the zoom button:

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.

Providing access to the Oracle Cloud for OTM would allow users to connect to the API's to deliver data sets from the Cloud and use it for workflow and other data management activities.

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.

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. 

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.

Idea

Currently

Hi everyone,

Add two additional features to a directory tool. Something like this:

Use cases:

1. Since it is not possible to use a folder browse on the Gallery, this could help a basic user create a list of possible folders to select from with the help of a drop-down

2. Directory analysis for cleaning purposes - currently, if you want to get a list of the folders with Alteryx, it takes forever for big file servers since Alteryx is mapping all the files

Both are achievable today through regex or a bat script.

Thank you,

Fernando Vizcaino

As an international organization we deal with clients in multiple-countries.

Name matches for names including Chinese characters generate a unicode conversation warning and are excluded from the fuzzy match.

It would be good if fuzzy match could be enhanced to handle Chinese characters.

Currently, the "SQL editor" window only contain a box for typing text in, we could not see the schema and table on it's side as a reference, we need to jump back and force between "Visual Query Builder" and "SQL Editor" search for table and column names. If we could see the database schema and table in the SQL Editor interface, it will save us a lot of time.

I try to use the Comment tool for documentation within workflows for team members (and my future self when I have to revisit it months after I built it). It would be helpful to be able to use markdown formatting inside the tool.

This might even encourage more documentation. *fingers crossed*

Hi, I was looking for this but couldn't find a similar idea, so I post a new one. If someone knows about a similar idea, please ask the moderators to mer

CountChars(<String>, <char to count>,<case sensitive>)

Where <char to count> and <case sensitive> are optional parameters.

If <char to count> is not provided, the funtion will return the total character count within the <String>.

If <char to count> is provided, it'll return the number of ocurrences of that character within the <String>.

PS: For those tempted to suggest a workaround, I've been using REGEX_CountMatches() for this. Actually, the focus is to simplify user's experience and workflow performance providing a native function, instead of using REGEX which it's very demmanding on resources.