Alteryx Designer Desktop Ideas

In a previous lifetime I spent a lot of time developing data processing workflows in Microsoft Access before moving into Alteryx as my primary data processing tool. Although Alteryx is, on the whole, vastly more feature rich than Access, Access has a couple of very simple features which Alteryx could integrate into the Browse tool to significantly improve its usability. In particular, I am suggesting the option to add a totals/summary row to the browse tool to calculate basic statistics for columns on demand. 

Attached is a screenshot of a totals row for a dummy table in Access. As you can see, a user can select from various summary statistics including sum, average, count etc. 

Almost every day I export data from the browse tool to Excel multiple times, simply to calculate column totals. A totals row in the browse tool would remove a major source of reasons for me to export to Excel and would significantly increase the browse tool's usefulness. 

Hello,

In cases where more than one field is being used in a join, the "Join (Tool ID) String fields can only be joined to other string fields" error message could be improved by indicating which field has a mismatch.

For example, if I'm joining Fields A, B, C, D... to fields Z, Y, X, W... in Join tool 24, and for some reason Field Z gets changed from String to Double, it'd be nice to see a message like:

"Join (24) (Field 1) String Fields can only be joined to other String fields"

or

"Join (24) String Fields can only be joined to other String fields (A)"

So that I know I need to go to a select tool and change the type of either A or Z.

Otherwise I look at the Join tool output and try to figure out which pair no longer has matching types, which can take a minute when dealing with a multiple-point join.

Thank you!

The Dynamic Input tool fails when attempting input a set of Excel files with the following error:

Error: Dynamic Input (1): The file "Test2.xlsx|||<List of Sheet Names>" has a different schema than the 1st file in the set.

Each spreadsheet contains two tabs and all tabs contain the same columns.

The root cause of the schema error is that maximum sheet name length in the two spreadsheets is different.  The first spreadsheet uses "East" and "West" for sheet names.  The second spreadsheet uses "North" and "South" for sheet names.  The Dynamic Input tool uses the longest sheet name when defining the effective Schema.

Excel limits sheet name length to 31 characters. It would be helpful if the Dynamic Input tool used 31 as the minimum string length when defining a schema from Excel sheet names.

The Input Data tool exhibits similar behavior when using a wildcard in the filename and the "Import only the list of sheet names" option.

A batch macro can be used as a workaround.

I'm Left handed and use my mouse in my left hand.  As such I use the following right-hand keyboard operations in the programs like Excel etc; CTRL-INS (Copy), Shift-INS (Paste), and Shift-DEL (Cut).

In Alteryx Designer these don't work for me in the Workflow window (but do in say the meta Info window) - is there a setting so I can enable them for the Workflow Window, or can the feature be added.

When I select multiple containers using control. I can see the configuration pane still on the left. If I adjust anything there it will only adjust the last selected container. I would like it to adjust all selected containers.

We would like some enhancements to the Salesforce connectors (input and output) to allow:

- Either the Batch or the Bulk API to be used. Batch API is much better for smaller jobs while the Bulk is better for larger jobs (larger numbers of records). It would be very useful to allow the selection of which API was used by the tool to use the most efficient API.

- The number of records per batch to be defined in the tool. I know this can be achieved using a batch macro but it would be far easier (from a user point of view) to be able to enter this value in the Salesforce connector and have it manage the batch size. We frequently have issues with the batch size being too large and Salesforce having errors (and records not updating).

Hi 

I think its super frustrating not beeing able to search for dates, or date ranges in the result window.

Lets say I have a dataset with 2 dates, date picked up and date delivered.

Then I need to search broad in the result window, for a given date. With search in both coloumns.

Could we please have a simple specific date search, and maybe a from-to date? Like in the filter?


Or go all the way and look at excel date filter?

Kind regards

Sometimes, when you change the system settings on Alteryx Designer, you get this annoying message :

Error: "Settings Validation Error" Alteryx Service failed to initialize, likely due to inconsistent RuntimeSettings.xml file: Unable to start Queue service, insufficient license

well, well, well...

I found the solution to this page https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Settings-Validation-Error-when-usin...

"Under Environment Setup Type, you must select "Designer Only" if only Designer is licensed"


Maybe instead of the current message, Alteryx can check the licence and help with a "you must choose Designer only option ath the beginning because only Designer is licensed".

Best regards,

Simon

As @Jonathan-Sherman pointed out in his blog post we love that the toolbar is back in version 2020.2!

One way that this toolbar could be enhanced, however, is to allow the use of the save button while a workflow is running. The user can still click File->Save while the workflow is running, but it would be quicker to be able to use the button on the toolbar.

Hello!
I have recently come across something within Alteryx that caught me by surprise. Currently when you are within the configuration window of a tool (in this example, the browse tool) and use ctrl + backspace (shortcut for deleting a previous full word), a blank character is instead added.

Please see example:

Currently in the Browse tool configuration

Go to change the Name of the tool - and naturally to clear it, use ctrl + backspace:

[] is added to the end. From what i can gather, this is a 'control character' , used when an application does not support ctrl+backspace.

Ctrl + Delete however, is supported.

I am proposing for this character/functionality to be supported. I believe the configuration window is the main - and potentially only, i couldn't find any other examples - place this is not supported.

Hope this makes sense!
TheOC

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

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.

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.

The data view of any anchor is searchable. I want to search the metadata view please.

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.

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.

Being able to specify a name for the FileName field in the Input Tool configuration would be helpful for cases where a field named FileName is already present in the input data and has a different purpose than the newly added FileName field. Instead of having to use Field Info and other tools to rename the last field into something else (i.e. AYX_FileName), this would be an easier approach.

Passing data to the next app running in a chain from the gallery varies from challenging to impossible. An impossible situation I've found is when the same user needs to run multiple instances of the app simultaneously. Very difficult is just allowing two different users to run simultaneously without risk of passed data mixing between the two.

This idea would add the capability to pass values from one app in the chain into user variables in the next app in the chain.

The C API for e1 is included in the Designer Desktop installation. The new AMP engine must have a C API as well, but it has not been released publicly.

Let tool and SDK makers create custom tools that plug into the AMP engine by releasing the specifications of the AMP C API.