Alteryx Designer Desktop Ideas

I'd like to be able to disable a tool container but not minimize it so I can still see what's in there. Maybe disabled containers could be grayed out the way the output tools are when you disable them. We would still need to retain current features in case people like it that way, but it would be nice to choose.

To keep from being too specific, the "Idea" is that Alteryx Designer should do better at recognizing and handling Date/Times on input. Thoughts include:
 
1) Offer more choices in the Parse: DateTime tool, including am/pm.
2) Allow users to add new formats to the Parse: DateTime lists.
3) Include user-added formats in the Preparation: Auto Field tool's library.
4) Don't require zero-padding of days and hours in the DateTimeParse() function.  (1/1/2014 1:23:45 AM looks enough like a date that DateTimeParse() should be able to figure it out, but it stumbles on day and hour.)
 
My particular difficulty is that I have incoming date/times with AM/PM components.  I've gone ahead and created a macro to take care of that for now, but it certainly seems like that sort of thing would be handled automatically.
 
Thanks!

A recent post solution (https://community.alteryx.com/t5/Data-Preparation-Blending/Can-somebody-tell-me-where-is-quot-Choose...) by @patrick_digan alerted me to a loss of functionality of the Input Tool.  In order to define a range of data via SQL to Excel (e.g. Sheet3$A1:C10) you need to know a work-around instead of just modifying the SQL.  The work-around is to modify the XML.  I would like to see that functionality returned to the Input tool.

 

Cheers,

Mark

Abiltiy to have multiple streams come into/out of 'Block Until Done' tool.
Allow User to set priorities of streams in tool and to be able to release streams in a certain order.

While I strongly support the S3 upload and download connectors, the development of AWS Athena has changed the game for us. Please consider opening up an official support of Athena compute on S3 like support already show for Teradata, Hadoop Hive, MS SQL, and other database types.

Bring back the Cache checkbox for Input tools. It's cool that we can cache individual tools in 2018.4. 

 

The catch is that for every cache point I have to run the entire workflow. With large workflows that can take a considerable amount of time and hinders development. Because I have to run the workflow over and over just to cache all my data.

 

Add the cache checkbox back for input tools to make the software more user friendly.

Alteryx Designer should automatically save my modules on a regular basis so that if I have a failure of some sort, my hard work will not be lost.

Hi all,

 

The Publish to Tableau Server tool is great.. but requires username and password. If you are using AD, there is a chance that your users don't have a password. In that case, you probably have a technical user that you share across the team. This is not an ideal situation and you loose the governance around the data. 

 

Fortunately, there is an easy workaround. You can leverage personal token authentication : https://help.tableau.com/v2019.4/server/en-us/security_personal_access_tokens.htm 

 

The advantage of this method is that it logs in with your user and your data source is uploaded under your name. This is still using the Tableau REST API so the changes to do in the current macro is MINOR. 

 

Changes to do in the current macro : 

 

1- Add a parameter authentication method with choices : Username/Password ; Personal Token 

2- If Personal Token is selected, add two parameters : Token_Name and Token_Value

3 - In the TableauServer.Login supporting macro, improve the formula(13) to change the payload based on user selection. If Username/Password, keep it as is. Else use the syntax here : https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm#make-a-sign-in-r... 

 

 

This is quite a straight forward change but could help a lot of companies using Alteryx.

Can you please implement that changes to strengthen this tool ? 

 

Thanks a lot,

Not sure what detail needs to be added.  This is obviously a widely used RDBMS.

Team Drives are shared spaces where teams can easily store, search, and access their files anywhere, from any device.

Unlike files in My Drive, files in a Team Drive belong to the team instead of an individual. Even if members leave, the files stay exactly where they are so your team can continue to share information and get work done.

The Input Tool reads Excel however many dashboards require multiple people to update a spreadsheet. Excel is too much of a hassle to share and update. Being able to read directly from a Google Spreadsheet would allow easy multiuser access to updating spreadsheets for dashboards.

Please add Google Spreadsheets to be an option in the Input Tool.

Tim

When posting an alteryx job to the gallery; or packaging them for transport - any deep dependancies are lost (I think that we start to have trouble once you're 3 levels deep).

 

For example - you have a canvas; which uses macros; which in turn have macros; which in turn have macros.

 

this is not as uncommon as it may sound on the surface - due to the current lack of flow-of-control support in Alteryx; we need to wrap all of our ETL jobs in Batch Macros to force them to run in a specific order.   Within these ETL jobs, it's common to decompose for lookups; master data management; etc.

 

Is this something that the team is currently looking into fixing - this does cause quite a bit of pain when deploying to the gallery because the jobs need to be manually stitched together and packaging does not carry the full working solution?

 

 

 

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

Add in-database tools for SAP HANA.

Please star that idea so we can prioritize this request accordingly

I would like to see more files types supported to be able to be dragged from a folder onto a workflow. More precisely a .txt and a .dat file. This will greatly help my team and I do be able to analyze new and unknown data files that we receive on a daily basis.  

 

 

Thank you. 

I have two use cases here:

1) A single tool that I want to connect to several tools (e.g. an input connecting to a number of selects)

2) Several tools that I want to connect to a single tool (e.g. several inputs connecting to a single union tool)

The current interface requires that I establish these connections by connecting the tools individually. It would be great to have the ability to have a right-click option. Simplistically, it might work something like this...

1) Select the tools that you want connected to a single tool (e.g. all the selects); Right-click; Get connection from Tool...{drop down list}

2) Select the tools that you want to get their connection from a single tool (e.g. all the inputs); Right-click; Connect to Tool...{drop down list}

Trying to solve some use cases, I realized that I had to simulate the factorial behaviour.

Having a factorial formula can make this process easier.

Thanks!

The option to open Hyper files in 2019.4 is great! For some of our use cases it would be even better, if we would be able to directly open Hyper files that have been published to Tableau Server.

 

It should be possible to achieve this by combining the Tableau REST API method Download Data Source, which returns a Tableau Packaged Data Source (.tdsx), which then would need to be converted to a Zip file to be able to navigate to the contained Hyper file.

We need some way (unless one exists that I am unaware of - beyond disabling all but the Container I want to run) to fire off containers in particular order.  Run Container "Step1" then Run Container "Step2" and so on.