Alteryx Designer Desktop Ideas

Currently, you have two choices for Auto Configure while working on workflows:

• Auto Configure switched on: After every change, the configurations (= columns) of tools are re-evaluated for the entire workflow (at least, this is how it feels like).
• Auto Configure switched off: Configuration of tools is only re-evaluated when pressing F5 (or when using the clipboard).

Pros and Cons of both:

• Auto Configure switched on:
  • Configuration in each tool is always accurate so that working on tools is straight forward.
  • Editing workflows gets annoyingly slow for complex workflows, especially when data sources from network locations or macros are used. Sometimes I have to wait a minute between two mouse clicks.
• Auto Configure switched off:
  • Editing workflows is faster (at least in theory).
  • I have to press F5 all the time (because I nearly always change output configuration of tools when working on workflows). Even after pressing F5, Alteryx does not always succeed in calculating the correct configuration of a tool.
  • Working with clipboard, loading, saving workflows is still slow.

I would love to have something in between all, kind of an intelligent Auto Configure with following features:

• F5 still starts full configuration evaluation.
• Configuration of input tools is frozen (unless F5 pressed) so that no network access is started during editing the workflow.
• Check for update of macro files is switched off (unless F5 pressed).
• After changing a tool configuration, either a flag is set that this tool was changed but no re-assessment of the workflow configuration is run (approach 1), or only downstream configuration is updated (approach 2). Whether approach 1 or 2 is started could be decided on various criteria: Number of downstream tools (or other measure of complexity), how many "change flags" according to approach 1 are already set, etc.
• If approach 1 was chosen: If you edit a tool which is downstream to another one for which the change flag is set, re-evaluate only the portion of the workflow between the previously changed upstream tool and the tool supposed to be edited.
• Using Clipboard should not invoke full re-configuration.
• Before saving a file, full re-configuration needs to be run (as already now).

This idea will add quite some complexity into the logic of Auto Configure but should have quite some potential to speed up editing workflows because network access and number of re-evaluated tools in each editing step will be reduced.

CI / CD is critical to any production level process, especially when multiple authors are contributing new features to the same workflow. Currently, multi-author editing of workflows is extremely difficult, and something that would be aided greatly by using git to control different branches of ongoing work. Luckily, that's something we can already do today! However, the ability to test before merging a pull request is critical to modern CI / CD pipelines. For this, it we need to be able to run a headless workflow from a CI / CD environment. Also, having the ability to pass in parameters to the workflow would allow for robust integration testing - something that isn't straightforward today without running on production environments. 

Often I need to add filters or other tools early on after the workflow is already been mostly built. If a tool connects to one tool I can drag the filter over the connecting line and add the filter seamlessly. However in large workflows there is often this situation:    

The Filter will only connect to one of the lines I'm hovering over. If I could connect to all lines simultaneously and drop in the connection to achieve this (would be awesome):

In workflow Constants, it would be really useful to be able to populate a new field associated with each user created constant. 

E.g. Type, Name, Value, "Description"

The description could be left blank but also populated by workflow designers to attach commentary / business logic to the constant. 

E.g. Type = User, Name = MyUserConstant, Value = 0.25, Description = "This describes the weighting factor used in Product Calculations"

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.

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,

Here is the proposal about an issue that I face frequently at work.

Problem Statement -

Frequent failure of workflows that have either been scheduled or run manually on server because the excel input file is sometimes open by another user or someone forgot to close the file before going out of office or some other reason. 

Proposed Solution - 

The Input/Dynamic Input tools to have the ability to read excel files even when it is open so that the workflows do not fail which will have a huge impact in terms of time savings and will avoid regular monitoring of the scheduled workflows.

Hello all,

As of today, when you want to retrieve or create a file on Apache Spark for Databricks, you have only two choices :  CSV and Avro

However it's clearly missing parquet file type :
-it's faster
-it's better for storage
-it's standard and already supported as input/output of Alteryx or for HDFS so doesn't seem hard to add here.

Best regards,

Simon

Formula Tool --> Functions --> Operators list

The operator titles for the two comment functions are too similar, the difference cannot be determined unless checking the hover text.

Can the title for /* Comment */ be adjusted to make it more clear that it is for block or multi-line usage?

I didn't understand the difference until I saw this post on LinkedIn:
https://www.linkedin.com/feed/update/urn:li:activity:7165816592063266817/

/* Comment */ --> /* Block Comment */   |   /* Multi-line Comment */

We will not be enabling DCM for the time being (see https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Enable-auto-complete-predictive-typi...).  

But, when you do not enable DCM, you get an annoying pop up every time you open Designer that says "DCM toggle is not enabled". 

Please give us the ability to turn this pop up off.

Hello All,

I'm using the dynamic input tool for SQL requests in my Workflow (WF).

I'm using the "Replace a Specific String" to replace elements in the SQL statement dynamically depeding on results of prevoius tools, user input etc.

So the statement looks like

select * from Schema_Name_xx where invoice_number = 'invoice_number_xx'

Since Schema_Name_xx is no valid Schema in the Database, the statement (= Validation) won't work. Only if I replace Schema_Name_xx by e.g. Invoice_Data_Current it will work, same with the invoice number, invoice_number_xx is replaced by e.g. 4711.

Therefore, validation makes no sense and will never work, only if the WF is running, the correct Schema is inserted in the SQL statement by the "Replace a Specific String" function.

It would be great to disable it in the users settings or wherever in the Designer, changing a config file would also be great :-)

Pls. note: I'm thinking (since I'm not allowed anyway ;-)) about changing/disabeling anything in the Alteryx Server settings.

Reason:

1. Speed: Validating a WF with SQL statements that don't work takes time (every time I save it), sometimes I get even a timeout...

2. WF error entries: Each upload with a  failed validation creates an entry in the WF result list which makes it harder to seperate them from the "real" WF errors...

Thanks & Best Regards,

Thomas

Changing the Macro Input tool in an existing macro is dangerous and can result in unmapped fields or lost connections in workflows using the macro. For example, we have a widely used macro for which we'd like to change the name of an input field, change it's default type from Date to DateTime, make it optional while keeping other fields mandatory. Currently, we cannot find a solution which would not require us to fix each workflow using the macro after changing it. We should be able to change the field names, field types (e.g. String to V_WString, Date to DateTime), select optional fields and do other modifications to Macro Input without having to update each workflow using the macro. The new Macro Input UI could be enhanced with a window similar to that of Select tool's. Technically, the Macro Input fields could have a unique ID by which they would be recognised in workflows, so the field names would just be aliases that could be changed without losing the mapping. In summary, we are restricted to our initial setup of Macro Input and it is very complicated to change it afterwards, especially if the macro is used widely.

Hello all,

A few weeks ago Alteryx announced inDB support for GBQ. This is an awesome idea, however to make it run, you should use Oauth2 Authentication means GBQ API should be enabled. As of now, it is possible to use Simba ODBC to connect GBQ. My idea is to enhance the connection/authentication method as we have today with Simba ODBC for Google BigQuery and support inDB. It is not easy to implement by IT considering big organizations, number of GBQ projects and to enable API for each application. By enhancing the functionality with ODBC, this will be an awesome solution.

Thank you for voting

Albert

When I import an Excel file in to Alteryx I get an error: “shared strings root=x:sst” and Alteryx cannot read the file.

I can work around this by manually opening and saving the excel before importing it into Alteryx but this is not ideal, especially considering the automation implications.

I believe this may be happening because the XLSX generated by the source of the report has a prefix “x:” in all the tags in the Shared String XML embedded in Excel. See: https://learn.microsoft.com/en-us/office/open-xml/working-with-the-shared-string-table 

Essentially, it would appear Alteryx is not able to read generated Excel sheets which has the prefix "x:" (e.g. from a bot). The second file which has been opened and saved in Excel manually can be read by Alteryx correctly.

Example of file as exported from ”BOT”:

How the same file looks once it is manually opened and saved:

Ideally Alteryx would read the file as is, i.e. with the "X:SST" tag seen above as having to manually open and save the excel before it can be read is rather clunky.

Thanks!

Hi there,

When creating a database connection - Alteryx's default behaviour is to create an ODBC DSN-linked connection.

However DSN-linked connections do not work on a large server env - because this would require administrators to create these DSNs on every worker node and on every disaster recovery node, and update them all every time a canvas changes.

they are also not fully safe becuase part of the configuration of your canvas is held in the DSN - and so you cannot just rely on the code that's under version control.

So:

Could we add a feature to Alteryx Designer that allows a user to expand a DSN into a fully-declared conneciton string?

In other words - if the connection string is listed as 

- odbc:DSN=DSNSnowFlakeTest;UID=Username;PWD=__EncPwd1__|||NEWTESTDB.PUBLIC.MYTESTTABLE

Then offer the user the ability to expand this out by interrogating the ODBC Connection manager to instead have the fully described connection string like this:
odbc:DRIVER={SnowflakeDSIIDriver};UID=Username;pwd=__EncPwd1__;authenticator=Snowflake;WAREHOUSE=compute_wh;SERVER=xnb27844.us-east-1.snowflakecomputing.com;SCHEMA=PUBLIC;DATABASE=NewTestDB;Staging=local;Method=user

NOTE: This is exactly what users need to do manually today anyway to get to a DSN-less conneciton string - they have to craete a file DSN to figure out all the attributes (by opening it up in Notepad) and then paste these into the connection string manually.

Thanks all 

Sean

Hello!
I like to annotate my workflows when finished, and it can be a bit of a pain to add more and more comment tools by searching for them, or going through the current right-click menu:

What would be nice is the option to right click anywhere on the canvas, and have the option of 'add comment', similar to how we have the option for 'add container' when selecting tools on the canvas.

Cheers!

When opening an Alteryx workflow that has been saved in a newer version, a warning message is shown, but you are still able to open the workflow, provided that it doesn't contain tools that don't exist in your current Alteryx version.

This does not work for packaged workflows that contain macros, for instance. You have to manually edit the xml of the extracted package file.

It would be great if we could have the same ability with packaged workflows that exists for normal workflows, i.e. the ability to extract and execute them with a warning.

The order of the join fields effects the ordering output

For more complex joins it would be nice to have up and down arrows much like the summarise tool:

It would be helpful if we could open 2 or more workflows at the same time from a gallery connection. Sometimes they are related or part of an overall update process, so opening all of them at the same time would save many clicks and a lot of time.