Alteryx Designer Ideas

Now that we have a Snowflake Bulk Loader option, it would be great to utilize the built-in Snowflake internal staging.  This eliminates the need for an end-user to have the technical know-how or access to IT resources to utilize a separate S3 bucket and generally reduces friction in the process. 

 

There was pretty widespread support in the original Bulk Load thread: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Snowflake-Bulk-Loader/idi-p/105291/page/2#co...

As a best practice, I'd like to automagically change any drive mapping to UNC when saving my workflows.  This applies to both local and gallery saves.

 

Cheers,

 

Mark

Hi All,

 

Data security is very important nowadays. There is no encryption for the output file from Alteryx Designer. 

Imagine, anyone who has Alteryx designer can open any yxdb even with the sensitive data. 

 

Suggest to add an encryption option in the Output Data tool.

 

Best Regards,

Samuel

I've had several of my users complaining about the Visual Query Builder view after the last couple of releases. When you maximize the window, half of the screen is taken up by blank gray space and there is no way to adjust it and it's very difficult for those who do not know SQL to build their queries in this very small white space. Need to be able to adjust the gray space.

 

 

In order to fully take advantage of Alteryx spatial features it would be great to have the ability of using Openstreetmap extract files natively.

While there are some sources available in SHP format they tend to be heavily cut down in detail, while the native OSM and PBF have the full feature set.

 

As it's an open format licensing shouldn't be an issue and it may pave the way to new features.

 

What do you think?

The idea is to store credentials, login/pw in a "credential alias".

 

Then, those credential aliases can be used in :

-traditional aliases/connection

-in database aliases/connection

-hdfs aliases/connection

-API

-on user aliases for connected controllers/gallery

...etc.

 

The idea is that I only have to change the credentials once for all the connection type (on Hive, I have the in db alias, the traditional alias and even an HDFS alias using exactly the same credentials !! and I have to change all that manually).

 

As a best practice, I'd like to automagically change any drive mapping to UNC when saving my workflows.  This applies to both local and gallery saves.

 

Cheers,

 

Mark

With the amount of users that use the publish to tableau server macros to automate workflows into Tableau, I think its about time we had a native tool that publishes to Tableau instead of the rather painful exercise of figuring out which version of the macro we are using and what version of Tableau Server we are publishing to. The current process is not efficient and frustrating when the server changes on both the Tableau and Alteryx side.

Statistics are tools used by a lot of DB to improve speed of queries (Hive, Vertica, etc...). It may be interesting to have an option on the write in db or data stream in to calculate the statistics. (something like a check box for )

 

Example on Hive : analyse {table} comute statistics; analyse {table} compute statistics for columns;

As of today, you can pass SQL from :
-input tool

-output tool

-connect in-db

The user interface is very limited, the kind of query you can pass also, welll, not very user-friendly. This generates a lot of frustration among users.

What do I suggest :
1/ A direct button "Query Builder" without having to open a new wf and drop an input box and then go with the presql tool and fight to build a query.

2/ Basically the same features than Dbeaver (https://dbeaver.io ) or DBvisualizer (https://www.dbvis.com/) or SQUIRREL http://squirrel-sql.sourceforge.net/ ):
  -Ability to pass any SQL Code I want (such as update, create, truncate, etc...) when I come from the button, "protected" sql when I am in a workflow
  -autocompletion

  -color coding (The idea is not new )

 
3/ A box "Free Sql Query" that I can branch on a indb or standard wf to pass any SQL query. The Output would be the same as input, just like it would be with a block until done.

I've had several of my users complaining about the Visual Query Builder view after the last couple of releases. When you maximize the window, half of the screen is taken up by blank gray space and there is no way to adjust it and it's very difficult for those who do not know SQL to build their queries in this very small white space. Need to be able to adjust the gray space.

 

 

The idea is to store credentials, login/pw in a "credential alias".

 

Then, those credential aliases can be used in :

-traditional aliases/connection

-in database aliases/connection

-hdfs aliases/connection

-API

-on user aliases for connected controllers/gallery

...etc.

 

The idea is that I only have to change the credentials once for all the connection type (on Hive, I have the in db alias, the traditional alias and even an HDFS alias using exactly the same credentials !! and I have to change all that manually).

 

This one may be a slightly niche request, but it has popped up a couple of times in my work so I thought I would submit.  When importing multiple sheets from an Excel workbook using either the Dynamic Input or wildcard in the Input Data tool, I sometimes get an error that the schemas don't match.  While this initially seems like the headers may be different, it can often occur because Alteryx is casting the columns as different data types (as I understand it, based on a sample of the incoming data).  While this is often helpful, in this case it becomes problematic.  

 

This has been asked several times on the discussion board including here and here. To workaround this issue, I have gone the batch macro route, but this could be solved more simply for the end user by adding an additional checkbox to the Input Data configuration when an Excel file is selected that imports all fields as strings (similar to the standard CSV input).  Then the schema could be specified using a Select tool by the user once all of data is brought in.

 

I'm not sure if this would be valuable for other input data types where a schema is more explicitly specified, but for any where Alteryx is guessing the schema, I feel like it could be helpful to give the user a bit more control.

 

 

Directory Tool retrieves today a lot of information about a file. I must say I appreciate getting easily the size and the last write time.

But why not the owner? I have developped a macro with a powershell to do that but what a nightmare for a so little piece of information.

It would be really helpful to have a bulk load 'output' tool to Snowflake.  This would be functionality similar to what is available with the Redshift bulk loader.

Currently it takes a reaaally long time to insert via ODBC or would require you to write a custom solution to get this to work.

 

This article explains the general steps but some of the manual steps outlined would have to be automated to arrive at a solution that is entirely encapsulated within a workflow.

http://insightsthroughdata.com/how-to-load-data-in-bulk-to-snowflake-with-alteryx/

Statistics are tools used by a lot of DB to improve speed of queries (Hive, Vertica, etc...). It may be interesting to have an option on the write in db or data stream in to calculate the statistics. (something like a check box for )

 

Example on Hive : analyse {table} comute statistics; analyse {table} compute statistics for columns;

use case : much of our users copy paste a formatted query to the Alteryx tools such as Connect in Db or Input Data (especially to reduce the data).

 

However, some of the formatting such a Carrier Return does not work

 

select 
 * from 
`re7_kerberos_za_e_*******_ee01pub_edd`.`v_*******_flux_20170511` 

 

 

The issue : we have to regurlary change our passwords. It implies changing it for all the connections alias (at least for standard connections). 

What I'm looking for :

A commande line to execute like :
alteryxpw.exe -connection {alias name} -connection_type {user/system} -connection_mode {standard/indb} -pw {new password}

This command line could be executed by a powerhsell script.

Right now in order to pass a parameter to pre/Post SQL we need to make a macro as a work around.

It would be really great if this was a native capability for the output tool so we don't have to replicate all the output too fields as macro inputs