Alteryx Designer Desktop Ideas

Frequently with more complicated tool configurations I end up having to setup certain elements over and over again.  Would be great to have a one click "use this as the default" configuration that would follow my profile and apply to all future drags of that tool onto the workflow.  Configuration elements that depend on the input fields would not be impacted.

Also an apply all feature to apply the similar configuration elements to all tools of the same tool type.

Example Configuration Elements

Comment Tool - Shape, Font, text Color, Background Color, Alignment...

Tool Container - Text Color, fill color , border color, transparency, margin

Table Tool - Default Table Settings

Union Tool - "Auto config by name", Actions when fields differ

Data Clensing - all configuration elements

Sample - all configuration elements

The sum function is probably the one I use most in the summarize tool. It is a silly thing, but it would be nice for "Sum" to be in the single-click list, rather than in the "Numeric" category...

Move sum function

There's often a need to do a cascade of filters which would normally be handled in a programming language by a Case or a Switch statement.

For example:

- if it's a cat then go left, otherwise go right 

      - if it's a dog then go left otherwise carry on right

             if it's a fish then go left otherwise carry on right

                   otherwise do xxxx

This could be handled more elegantly by a conditional split tool that allowed you to specify multiple conditions like a case statement, and which then generated multiple output nodes; with the last one for any leftovers.

Despite being an Alteryx user for 2 and a 1/2 years this is something I have only recently came across but it does not appear that you are able to use debug mode appropriately with macros.

What I mean is, I have a macro input which drives a series of drop down boxes. In debug mode my drop down boxes will not populate. Now I understand why, Alteryx doesn't know what the input is so it doesn't generate the meta data for the debug mode drop downs.

What I suggest Alteryx do is automatically convert your macro inputs for file browses for the purpose of debug mode (I had to do this myself manually and it was a tedious task, not only to set up but then maintain two separate versions, one essentially an application and one a macro).

Or, by default debug mode uses the macro input data to run through debug mode as.

Ben

The new Interactive Chart is a great tool that I've been using. A big improvement to it would be to allow a secondary axis, as well as allowing data points to show on the chart. I have attached a sample chart that was created in Excel. 

I'd say that 95.437% of the Joins I do are straight Inner Joins.

So each of those times I have to remember to go down to the Select part of the Join tool and deselect all the fields I joined on the Right Side since they'll be duplicates.

I'd like a checkbox like below (defaulted to CHECKED)  to deselect all the joined fields from the right hand side. In the rare cases where there's a need I could uncheck it.

Deselect R join fields

When documentin alteryx screen I sometimes hit printscreen and need to paste important matters to Comment tool...

But there is no paste from clipboard 😞

I suggest adding a minor icon that enables not only reading from png but pasting a screen or other image copied directly from memory...

For I need the following setting so I printscreen and capture as is;

Then put that into a PNG or JPG file using paint. And then prepare a comment box with that image in the background...

As a designer, I need to output data only when no data quality errors are encountered within a workflow.  I suppose that I wouldn't want to see any errors, but if I am writing multiple output files and errors are encountered during the output processes (e.g. #3 of 4 fails), then I'm kind of out of luck.  So let's focus on data quality.  If Nulls are encountered in "Actual" data or unjoined records are found or dates are out of range, you name the issue, I don't want to output any data to specific output tools.  Work-arounds exist.  I can output to a staging file and conditionally schedule or use a conditional runner macro to output to the production data.  But what I really want to do is to stop an output tool from receiving any data to output.

Today I handle this by counting error records that would be caught by a TEST tool and appending the count of these bad records to the data that would go to output(s).  I filter for IsNull([Count]) and only when 0 ERRORS are found by the test tool, can data be output.  Otherwise null records are received by the output tool and it quietly makes no changes.

My ask is to configure an output tool to be disabled if ERRORs exist.  That means that the LAST thing to happen in the execution of a workflow will be the output processes.  They will all be blocking tools and can't happen until there are no tools left to run except for the outputs (configured as blocked).  Maybe this is a big ask.

Hello,

I would like to suggest the ability to manage our virtual environment for Python modules within Alteryx. Some current workflows I am building would be far easier and more secure if I had access to the virtual environment that the Python code would run in.

Uses for modifying the virtual environment:

     1) Setting environment variables in order to hide API Keys/DB credentials/etc.

     2) Installing private GitHub repository packages into the environment.

     3) Creating repeatable and easily maintainable ways to manage dependencies. 

It would be important that these virtual environments have a way to persist onto Alteryx Gallery, so that workflows behave identically on local machines as they would on the server. This could potentially be done though a requirements.txt file or some other environment initializer, but I'll leave the implementation to the experts. My preference would be for each workflow to contain their own virtual environment (as is best practice when developing Python scripts). 

Thank you,

I do a lot of work with SQL code in the PRE/POST SQL options and when I get an error, it usually returns the entire code and a little bit about what is wrong. These long strings are hard to read in the current tooltip format as if you hover over to see the entire error, the tooltip goes away after 5 seconds. So I am frantically reading through lines of error code 5 seconds at time. Can we make it so the tooltip just hangs out until I move my cursor off of it?

When building a workflow with testing tools, you tend to want to be able to put these in container and then minimise this to improve readability of the workflow.

For example instead of this:

You might want to minimise the error checks like this:

However when running apart from reading through the results window, there is no immediate indicator that there is a tool inside the container that has errored:

So the feature enhancement request is to add in an exclamation marker to show the user that a tool inside has an error and you can then easily open it up and investigate further.

When saving an alteryx module (yxmd, yxmc, yxwz, yxzp), can we have a simple "SAVE AS" function that allows us to choose the version number?  Conversely, could we open a newer version module with a warning message rather than an error?

In either case there would be the logical CAVEAT that certain functions or features may not be compatible with the save/open function.

Thanks,

Mark

This functionality won't be mission-critical to anyone, I'm sure, but a lot of IDEs and upgraded text editors (lookin' at you Notepad++) have the ability to customize the colors of text, the background, and other various tabs/objects that may appear on the screen. I understand that this is more important for code-based systems where the coloring improves readability so much, but I thought it might be a neat feature. I think leaving the tool colors standardized is a good idea though, just the canvas and outerlying windows. It could include the colors for the formula syntax highlighting too?

The icing on the cake would be the ability to save and share your settings or create a repository for them in the public gallery or something.

Currently if I drag a tool onto the canvas and it has multiple input anchors, Alteryx will try to connect to the first input anchor from the output of the nearest tool I am hovering near.

However the improvement I would like to see is where there are specific tools which are required to go into each input that it 'intelligently' connects to the correct input, for example on the gif below I have a PDF input and PDF template tool (pre-computer vision), and when I bring the image to text tool in, it will try and connect the output of the template tool into the D input anchor, when the correct input is the T anchor. What this leads to is me having to delete a connection and then re-wiring which slows down the development time.

When we have too many steps in a workflow, it is mandatory to use container to represent better business flow. It can collapse many steps to represent one business flow.

But, when we open collapsed tool container, workflow canvas not resizing to give space for tool container, it overlap on existing tools.

It is better to resize workflow canvas when we collapse or resize tool containers. 

One of the most common causes for Admin trauma for our central Alteryx Gallery team - is dealing with drivers that may not be on the server; or a particular worker; or on a designer.

What we're looking for, is for the Alteryx team to maintain a packaged set of drivers as a single installer - which we can download at the same location as the Alteryx designer / server versions.

This would allow us to have 1 version of all drivers across ALL designer clients; as well as on our workers and servers.

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

While Alteryx does have a UNION set operator, it only currently has an Inclusive Union

the other two set operators, Intersect & Except, and an exclusive Union would be helpful if they can be added.

• Exclusive Union: Union two sets, but eliminate full duplicates (across the full row)
  • Although this can be done with a union, followed by a distinct - you have to do a distinct across all columns
  • This is the difference between SQL "Union" and SQL "Union ALL"
• Intersect:  This is the intersection of two sets - where the full row (all columns) are identical
• Except: This is where the row in 1 set is not in the other.

Intersect is particularly helpful for operations like looking at multi-column reference data to see if any fields at all have changed (like a slowly changing dimension).

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

// This is my new formula
MAX([Price] * [Quantity],0)
// This was my old formula
// [Price] * [Quantity]

Imagine being able to SELECT your text block (could be many lines) and right-clicking to see an option to Comment or Un-Comment those configuration statements.  I thought that you'd like it too.

Cheers,

Mark

When copying and pasting the datetime tool, or disconnecting its input, it loses its configuration. This can be really frustrating if it has an unusual formula, and can result in looking up the datatime functions again: https://help.alteryx.com/current/designer/datetime-functions and working out how to reconfigure the tool.

Steps to reproduce this issue:

1.  Set up datetime tool

2. Delete Input Connector:

3. Reconnect and notice the formula is missing and it has been reset to a completely fresh DateTime Tool:

Proposed solution:
The Datetime tool should remember the previous configuration, and go back to this when the input is deleted or it is copy pasted. It will then be able to be reconnected.



Steps in proposed solution:
1. Setup Datetime tool

2. Delete input Connector (Note the DateTime Config and Annotation Remaining, but still being not editable)

3. Reconnect the tool for it to still be configured for the data