Alteryx Designer Desktop Ideas

It would be nice to have an option to distribute tools with the fixed default space of three in between each tool. Now it just distributes based on the available space, which can be inconsistent throughout the workflow.

Adding "Lightning Bolt" connectors to the standard workflow tools to allow dynamic automation of the settings would be a game changer. I believe that this would enable us to create universally dynamic and adaptive workflows which could be used as drop in solutions for most datasets. This would turn the standard tools into a dynamic ones and dramatically reduce the tool count to accomplish dynamic tasks, and make complex workflows much easier to internalize. Making standard workflow tools more dynamic would allow us to easily dynamically incorporate conditional tests / values / fieldname selections / bypass / etc into tools like detour / filter / formula / unique / transpose / crosstab / summarize / Outputs / etc. I would also like to see the ability to utilize a bool field to bypass any given tool in a workflow. That way we could do things like conditionally bypass an entire formula tool which would dramatically simplify complex formula construction, turn on and off inputs / outputs, simplify error avoidance, etc.

In order to build complex dynamic conditional workflows with the current tool capabilities, most of us are forced to use custom macros (often a multitude of workflow specific ones as well), constantly add and remove formula created fields for message relay, and create complex multi-routings / tests / unions in a standard workflow with large numbers of tools and containers. This hides many of our tasks within short-term use fields / custom macros and it makes the rest of our workflows voluminous and less intuitive.

On the User Interface side, I recommend a simple approach. Next to the standard tool setting there should be a dynamic input option which allows you to select the source field in the lightning bolt connector. Next to that, there should be an icon that can be clicked on to pop up a short text description and a basic screen shot of data in the correct format for dynamic input. I would also like to see a check box at the bottom for manual tool "bypass" which can also be dynamically controlled. (This would especially be helpful on outputs, but it would also be helpful to allow formulas and filters to be kept in place for future use even when they should not currently be used) Turned off tools could be highlighted in a red background or something.

This would be useful for anyone creating dynamic and adaptive workflows, but it would especially expand Alteryx Designer's capability to attract more custom software developers like me.  It would dramatically reduce the need for a large number of complex workflow specific macros that clutter our systems. Users that find the traditional workflow tool approach easier for them could easily use the tools as normal by simply using the standard manual settings. Advanced users could simplify the creation of universally dynamic and self adaptive workflows.

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.

In short:
Add an option to cache the metadata for a particular tool so that it doesn't forget when using tool that have dynamic metadata such as batch macros or alteryx metadata engine can't resolve such as python tool.

Longer explanation:

The Problem:

One of the issues I often encounter when making dynamic workflows or ones that require calling external services is that Alteryx often forgets the metadata of what columns to expect. This causes the workflow to forget configuration of downstream tools when a workflow is first opened or when the metadata engine refreshes. There is currently the option to disable the metadata engine from automatically refreshing but this isn't a good option because you miss out on much of the value it brings.

Some of the common tools where I encounter this issue:

• Json parse
• Batch macros
• Python tool
• Regex parsing to rows

Solution:

Instead could we add an option to cache the metadata for a particular tool, this would save the metadata from the last time the workflow ran to within the workflows XML so that it persists when closed and reopened. Then when the metadata engine runs when it gets to this tool instead of resolving the metadata from the tool it instead uses the saved version in the XML. Obviously when it actually runs it would ignore this and any errors would still occur.

This could be an option in navigation pane of each tool. Mockup below:

This would make developing dynamic workflows far easier and resolve issues of configuration being lost when the metadata changes and alteryx forgets the options.

Hi there,

When you connect to a DB using a connection string or an alias - this shows up in the Workflow Dependancies in a way that is very useful to allow you to identify impacts if a DB is moved or migrated.

However - in 2023.1, if you use DCM then the database dependancies just show up as .\ which makes dependancy management much more difficult.

Please could you add the capability to view the DCM dependancies correctly in the dependancy window?

BTW - this workflow Dependancy Window would be a great place to build a simple process to move existing DB connections to a DCM connection!

CC: @wesley-siu @_PavelP 

Hello All,

I am not sure whether my idea makes sense or not. 

In today's advanced analytics world, we used RPA for various automation, process simplification, etc. There are CO-BOTs that are designed to run the Alteryx flow as well. Through RPA we are able to log in to the system and tools like Cognos, Oracle, TM1, and so on.

So, I am thinking, if Alteryx developed RPA as a tool in the Alteryx Designer like other tools such as Join, Transform, ML, Computer Vision, Interface, etc. 

I believe the implementation of RPA in Alteryx will prove an Asset, and make Alteryx.com more powerful.

Thanks,

Mayank

For very complex canvases and api data pulls that take a long time, it would be great that as we're working through the canvas to put flags or some setting that would allow us to keep data already pulled into a tool. This way I can set a certain tool to keep all of its data and then all tools i work on from that point forward will pull from that tool rather than from the beginning of the canvas.

for ex.

input tool --> api tool --> formatting tools --> new tools being worked on

if i can set the end of the formatting tools to keep all data then when i run the canvas only the new tools being worked on would get refreshed

i hope that's clear... currently it's very frustrating that any small change i make, i have to rerun the whole canvas and that takes a while

Please add in a feature to connect to S3 via AWS IAM roles.

This is purely aesthetic but it would be great to have a button to auto format tools positions on the canvas. The idea would be similar to a feature many IDE's come with to auto format code so that the indentation is corrected and duplicate return characters are removed.

We currently have the Align and Distribute capabilities which is great. This could be expanded to the entire workflow so that the canvas could look at which tools connect to which and structure their positioning around that. I think it would be a great clean up feature after finishing a workflow. 

If an Output Data tool fails, there are frequently other processes within the workflow that depend on the status (success|failure) of the output. I find myself having to build a macro or some other overengineered method to validate the status of the Output Data tool. Instead, please put an output anchor on the tool. Then, if there's an error, no downstream process will run and this will greatly simplify error handling. Thank you.

The most difficult part about quickly sharing Community Questions and Solutions is constructing representative "Dummy" data values as static Text Inputs that can be packaged in a workflow. Most of us are almost exclusively working with sensitive client and company data that cannot be shared. It would be great to have a tool that converted values over to dummy values based on the type of data in that field. Kind of like a dynamic find and replace that randomizes values, replaces occurrences with similar dummy values, or scrambles string values in an indecipherable way.

The tool output could directly update a connected "Create Text Input" tool, or it could be connected to a browse tool that could quickly be converted to a Text Input.

It would be very helpful if there was a tool that could stop the workflow without throwing an error. Currently, you can use the message tool to throw an error on a certain condition, and then enable the "Cancel Running Workflow on Error" option in the Runtime settings, but when the workflow is stopped in this way, many other tools don't function such as the Output Data and Email tools. Simply adding a tool that stops the workflow without erroring that also allows the other tools to finish their job would be great. 

To enable a check mark kind of option to lock or edit the configuration window of each tool.

It could be very useful to keep safe the settings in the configuration window.

Alteryx Gods,

Following a discussion with a person with whom I spend way too much time, @Jeff_Neklason , we were wondering would it be possible to allow users to drag and drop the position of the actual sections at the top of the designer?

Some users find they use the Developer section more than the Parse section, for example, and it would be beneficial if they could move the Developer section to the left to be more easily accessible.

Thank you Alteryx Gods.

I love you.

Kisses.

xxx

Hello Alteryx Dev Gurus - 

We are migrating and some workflows that used to successfully update a datasource are now giving a useless error message, "An unknown error occurred".  

Back in my coding days, we could configure the ORM to be highly verbose at database interaction time to the point where you could tell it to give you every sql statement it was trying to execute, and this was extremely useful at debug time.  Somewhere down the pipe Alteryx is generating a sql statement to perform an update, so why not have something on the Runtime tab that says, 'Show all SQL statements for Output tools'?  Or allow it on an Output tool by Output tool basis?  If this was possible by changing a log4j properties file 15 years ago, I'm pretty sure it can be done today.  

Thank you for attending my TED talk on how allowing for detailed sql statements to bubble back up to the user would be a useful feature improvement.  

Alteryx offers the ability to add new formulae (e.g. the Abacus addin) and new tools (e.g. the marketplace; custom macros etc) - which is a very valuable and valued way to extend the capability of the platform.

However - if you add a new function or tool that has the same name as an existing function / tool - this can lead to a confusing user experience (a namespace conflict)

Would it be possible to add capability to Alteryx to help work around this - two potential vectors are listed below:

- Check for name conflicts when loading tools or when loading Alteryx - and warn the user.   e.g. "The Coalesce function in package CORE Alteryx conflicts with the same function name in XXX package - this may cause mysterious behaviours"

- Potentially allow prefixes to address a function if there are same names - e.g. CoreAlteryx.Coalesce or Abacus.Coalesce - and if there is a function used in a function tool in a way that is ambiguous (e.g. "Coalesce") then give the user a simple dialog that allows them to pick which one they meant, and then Alteryx can self-cleanup.

cc: @JarrodT  @NicoleJ 

I would love a tool to be created for looking up a value in a table based on a condition. It could be called "Lookup." One input to the tool would be the lookup list, the other is the main database. Inside the tool you could enter functions that can query the lookup table and return the results either as an overwrite of an existing field in the main DB or as a new field in the main DB, similar to the options in the Multi-Row Formula tool.

Here is a link to my post in Community that explains the problem. The solution, in a nutshell, was to create a Join (which resulted in millions of additional rows), run the conditional formula, then filter to get rid of the millions of rows that were created by the Join so only those that met the condition remained (the original database rows).

Here is the text of my Community post describing my project (slightly modified for clarity):

Table 1:  A list of Pay Dates (the lookup table)

Table 2:  Daily timekeeper data with Week Start and Week End Date fields.

The goal:  To find the Pay Date in Table 1 that is greater than the Week Start Date in Table 2 and no more than 13 days after the Week End Date in Table 2.

[Table 2: Week Start Date] < [Table 1: Pay Date]

and [Table 2: Week End Date] < [Table 1: Pay Date]

and DateTimeDiff([Table 1: Pay Date], [Table 2: Week End Date], 'Days') <= 13

There are many different flows I could use this type of tool for that would save time and simplify the flow.

Thanks!

Hello all,

Sometimes, when you have too much time to retrieve your tables metadas, you can have this message

Initialization Timed Out: Workflow must be run for field meta info to be accurate.

From what I understand, it's Alteryx and the source system that drives the time out value. However, I have some cases where the long time is "normal" and that really hurts the user experience.
So, I would like the ability in settings to change the default value.

Best regards,

Simon