Alteryx Designer Desktop Ideas

Improve HIVE connector and make writable data available

Regards,

Cristian.

Hive

Please add Parquet data format (https://parquet.apache.org/) as read-write option for Alteryx.

Apache Parquet is a columnar storage format available to any project in the Hadoop ecosystem, regardless of the choice of data processing framework, data model or programming language.

Thank you.

Regards,

Cristian.

I have many aggregation in the same workflow which product one or two different column each, total could be xx different columns. Wouldn't it be nice to have a multiple append tool that could take connections from many other tools? At the moment I would have to use many separate append fields tools and then one transpose, or multiple transposes and union. Either way you have to attach something to each tool. 

Functions such as Year([Date Field]), Month([Date Field]), and Day([Date Field]) would really help with date-based formulas and filter tests.

It would be helpful to have the Read Uncommitted listed as a global runtime setting.

Most of the workflows I design need this set, so rather than risk forgetting to click this option on one of my inputs it would be beneficial as a global setting.

For example: the user would be able to set specific inputs according to their need and the check box on the global runtime setting would remain unchecked.

However, if the user checked the box on the global runtime setting for Read Uncommitted then all of the workflow would automatically use an uncommtted read on all of the inputs.

When the user unchecks the global runtime setting for Read Uncommitted, then only the inputs that were set up with this option will remain set up with the read uncommitted.

Although we can write a temporary file with all the parameters used it would be very helpful to pass simple parameters (or go all the way) between the Apps. I imagine any parameter created using Interface Tools should be available throughout the whole Chained App. 

There is "update:insert if new" option for the output data tool if using an ODBC connection to write to Redshift.

This option really needs to be added to the "amazon redshift bulk loader" method of the output data tool, and the write in db tool.

Without it means you are forced to use the "Delete and append" output which is a pain because then you need to keep reinserting data that you already have, slowing down the process.

Using the ODBC connection option of the output data tool to write to Redshift is not an option as it is too slow. Trying to write 200MB of data, the workflow runs for 20 minutes without any data reaching the destination table. End up just stopping the workflow.

It would be good to have the ability to select what column to use for Primary key when using the "create new table" output option of the output data tool.

When using the "update: insert if new" output option, you receive the error "Primary Key required for Update" if table does not have primary key.

Workaround is to manually create table with primary key constraint.

Please evaluate the option to add 2 new containers:

1. parallel - execute tasks inside in parallel
2. serial - execute tasks in strict  order, imposed at design time. In the future the oder of operations could be enforced by parameters or other input conditions at runtime.

Please Give us the capacity to mix and match these 2 containers.

Thank you

Regards,
Cristian.

I would like to suggest to contemplate the option to add a new SDK based on lua language.

Why Lua?

o is open source / MIT license

o is portable

o is fast

o is powerful and simple

o Lua has been used to extend programs written in C, C++, Java, C#, Smalltalk, Fortran, Ada, Erlang

My client today asked if Alteryx could be configured to build/run horizontally from right to left.  Thought I'd post the idea. 

Currently the Save Field Configuration, when used with fields in a different order does not give any indication that the ordering will not be saved and reused. It is possible people may use this option without realising.

This should be in the help at a minimum, perhaps in a warning box when used too, but ideally the renames and types should be applied to the columns they came from by Name - not just based on the order of the fields.

The "Field Summary" tool and several others have a configuration requirement that provides a list of fields to select or deselect.  The selection action is singular meaning you can only effect the action on one item in the list of many.  As the number of fields we work with grows significantly this becomes a time consuming and tedious task.

This should be enhanced to allow highlighting of multiple fields to select or deselect as we can do in tools like the "Select" tool.

The field summary tool is an excellent resource to get an overview of the data and spot targets for analysis or data cleansing. 

Unfortunately it has limitations either in the number of fields included or some combination of the number of fields and one or more of its attributes.   There is nothing in the documentation I found to make a user aware of this. When you exceed N  fields selected the system just hangs, indicating it is running but there is no connection progress shown and nothing seems to happen, even if you limit input to 1 record.

Through trial and error I found an approximate limit in number of fields I can include and still have it work.

I request that Alteryx update the tool help info and devise enhancements to dynamically load balance the tool so it can scale to the number of fields requested or at least warn when the limit is reached or approached.  The latter warning could be similar to the red font warnings in the formula tool when you have a malformed expression.  However a load balancing version is most desired.

The issue as it stands results in users wasting a lot of time trying to make the tool work as expected, then report it to support as an apparent bug in the tool which can be argued both ways.

I realize in the real world there are limits but in this real world we are seeing the number of fields to analyze increase significantly, especially when you have a data license and integrate 3rd party data to you own native data adding a hundred or hundreds more fields.

I know there is an idea for Dynamic Summarize, however I think with only small change to Summarize tool this could be achieved. 

If we set the Summarize to Group by all our dimensions but then use ListBox + Action to control which dimensions we want to select - wouldn't it be nice (ahh Beach Boys comes to mind) to be able to tell Summarize tool that if the dimension in group by is not found just ignore it? At the moment it throws an error. I just think such small configuration would achieve this, right? 

Please let me know what you think

For the Output tool, File Format of Microsoft Excel (*.xlsx) - the non-Legacy one - it doesn't have the "Delete Data & Append" option that the Legacy ad 97-2003 Excel formats have. 

Having the Delete Data & Append for the most recent version of Excel would be very beneficial. Without it, there does not appear to be a way to udpate an existing Excel sheet using an Alteryx workflow while preserving the formatting within the Excel sheet. The option to Overwrite/Drop removes all formatting. 

I have this workflow refreshing an Excel sheet daily, and then am emailing it to a distribution at the end of the workflow. Unfortunately, right now I have to use the 97-2003 format to preserve the formatting of the Excel sheet when it is automatically refreshed and emailed each day. 

Can you please assess adding this option? Thanks!

How about adding the ability to split intersecting trade areas at the points of intersection to create two new spatial objects.  The two objects could then be used to process customer records and divide them into "territories" based on  the line of intersection.

Please asses the value of using d3js javascript library to create vizualisation.

D3 gallery examples

Thank you.

Regards,

Cristian.

Please asses the value of having hdf5 as data input. A possible workflow could be:

HDF5 => | Processing tasks |  => export to Tableau (.tde) or Qlik (.qnx) => vizualisation workflows

Thank you.

Regards,

Cristian.