Alteryx Designer Desktop Ideas

The constant [Engine.GuiInteraction] can be used to determine whether a workflow was run in the Designer or Gallery. Currently, there's no method to also find out whether a workflow was initiated by a schedule or run manually in the Gallery. The information is available in the Gallery but not forwarded to inside the workflow.

Please introduce a new variable [Engine.ScheduledRun] (or similar) which determines whether the workflow was initiated by a schedule (value "true" if boolean or "schedule" if string type) or manually (value "false" or "manual").

It doesn't seem that Alteryx tests data that isn't on the same hard drive. If my data is located locally, Alteryx works great. If my data is located on a shared server, OMG it takes forever for it to do anything. Simply clicking off a tool onto the canvas can cause a 30-60 second freeze/wait. I literally spend about 1-3hrs per DAY waiting for Alteryx to simply load a tool view. 2024.2 is the worse so far, I have to wait for it to do anything.

It seems Alteryx is getting worse and worse at this, processing non-database data that isn't located locally on hard drive. My idea is to get better at this.

Additional Dynamic Select Mode for All Native (Non-Macro) Tools with Select Functionality (with or without Data Type Selection)

This is the updated version of an idea I posted a while ago (which only included Multi-Field Formula), and after the release of Alteryx Designer 2025.1, which I found to be very successful from a new tool and functionality perspective, I decided to post about it.

My proposition is to add the Dynamic Select functionality* (at least the Select via a Formula mode) to all native (non-macro) tools in all tool categories that include a Select functionality (as an alternative, where the user would be OK with not being able to also change the field types of the selected fields, such as Join and Append tools, the opposite would apply to Multi-Field Formula, where the user would be able to dynamically select which fields the Multi-Field Formula would be applied to, in addition to changing the data type), including but not limited to (to account for any new tool with a Select functionality that might be added in the future):

Preparation Category

- Auto Field

- Data Cleanse Pro (added in 2025.1)

- Multi-Field Formula

- Multi-Row Formula (for Group By option)

- Rank (for Group By option)

- Record ID (for Group By option)

- Sample (for Group By option)

- Tile (for Group By option)

- Unique

Join Category

- Append Fields

- Find Replace

- Join

- Join Multiple

Transform Category

- Arrange

- Cross Tab

- Make Columns (for Grouping Fields (Optional) option)

- Running Total (for both Group By (Optional) and Create Running Total options)

- Transpose (for both Key Columns and Data Columns options, the tool would generate an error if the Dynamic Select formula written for both options are selecting the same field(s), as the Transpose tool is not supposed to allow it)

- Weighted Average (for Grouping Fields (Optional) option)

In-Database Category

- Select In-DB

Reporting Category

- Layout (for Group By and Per Column Configuration options)

- Table (for Group By and Per Column Configuration options)

Machine Learning Category

- Transformation (for Select Features mode only, as the other two modes with Select functionality (Clean Up Missing Values and One Hot Encoding) require Method and Missing Category Action specification)

Developer Category

- Download (for And values from these fields option present in Headers and Payload tabs)

- Dynamic Rename (for the Select functionality present in Formula mode)

Spatial Category

- Find Nearest

- Spatial Info

- Spatial Match

Data Investigation Category

- Pearson Correlation

Skipping Address and Demographic Analysis categories as they have tools that seem to be using a static input, therefore not requiring a Dynamic Select functionality.

Laboratory Category

- JSON Build (for Grouping Fields (Optional) option)

- Transpose In-DB (with a similar logic to the regular Transpose tool found in Transform category)

*The Dynamic Select functionality added tools that have more than one input anchor (such as Join and Join Multiple) could have new additional fields the users can utilize, such as:

- [Origin] (can have the values "L" or "R" for Join and Append tools)

- [Connection_ID] (can have the values 1, 2, 3 etc. for Join Multiple tool)

- [Unknown] (can have the values "True" or "False" for the Data Columns option of the Transpose tool, or any other tools such as Join that would have the Dynamic or Unknown Columns option as a part of their Select functionality)

Hi,

I was wondering if would be great to have something like TEST RUN. Where it would check all settings of the tools. 

Example -  I have workflows that pull a lot of data, do some calculation and at the end they post to Tableau. It happens from time to time that my Table Token has expired so after running for like 3 hours I am getting error for the Tableau Tool. Or similar situation with output to excel to discovered that I have choose to Create not overwrite the sheet and have to re-run the workflow. 

It would save me a lot of time when I could just do a Test Run for all the tools to make sure that everything is set correct and I am good to run the workflow and start pulling down all the data. 

Not sure if this is possible but I am pretty sure that I am not the only one with this issue :)

Hello,

As of now, you can't choose the DCM connections to synchronize. It's either all or none.

However, I have one designer and two servers (Sandbox/Production). Most connections must be common, but not all.

Best regards,

Simon

When using certain tools, particularly market place tools like the SharePoint input/ output etc. it would be helpful to have a quick way to find out which version is being used in a workflow. Something along the lines of an option when you right click the tool, that displays the current version would be ideal. 

This would be helpful in several cases but primarily when handing over workflows. There are cases when I have multiple versions of the same tool installed so that I don't have any issues inheriting workflows. This does however, make things confusing when handing workflows back. Tool Version Labelling would solve this problem.

Regards - Pilsner

sometimes we deal with hundreds of columns and it's hard to scroll and locate a specific one in the Data panel.

In the Metadata panel it's easier to locate the fields by scrolling vertically, however it would be even easier if we could click on the 'Name' column header and have that temporarily sorted so as to quickly locate a given column.  (This would be IDEA 1).

Additionally, but not necessarily dependent on IDEA1, if we could have the Record number of each of the fields in the metadata, also included alongside their respective names in the Data panel, that would make it for much easier location of particular fields in the Data panel, as users could look for a given field in the Metadata, find their 'order number' and then switch back to the Data panel and scroll directly to that number.

Additionally, column name search buttons could also be added to both Data/Metdata panels for a 'contains' like field name search.

Thanks!

I would love to see an option to run only one container without having to disable all others (and tools not in containers).

I've got workflows with MANY different queries/tools each in their own containers and some tools outside of containers.  Occasionally I need to run or re-run just one of the containers (usually several times when the datastream contains Crosstab or Transpose tools where some fields/options will not populate until the workflow has previously run).  Normally I'd either have to disable all other containers and/or select EVERYTHING that I do not wish to run an add them all to another container that I could then disable.  An option to disable everything outside of a specific container would be most welcome and save a lot of time!

Vanilla Alteryx Chained Apps can only progress linearly, which means developers could not let users skip few applications ( or ) reach the last app in the chain ( or ) let the user select which specific app to trigger based on the requirement.

 

This can be bypassed by using a render tool with output as PCXML and HTML link of the Application you can trying to divert to, which does not affect the existing workflow in any way.

By using the below set of tools on any workflow/chained app you can either branch the flow of apps ( or ) you can skip a few apps in the chain.

1. A excel or csv file which has the links of the apps -  the reason for keeping the hyperlinks in an external file is so that we can update the link if the server link changes/updates - refer Image 1
2. A filter tool to specify which application to move to ( can be changed using a radio button/drop down to app 2/3/4/5 etc.)
3. A text tool ( This is where the magic is ) - configure it to pick the server link from the incoming data from the filter tool as hyperlink and generate a output preview, as shown below - refer Image 2
4. Use a render tool as output and write to any PCXML file ex: "File.pcxml" - refer Image 3

Image 1 - Input Configuration with the flow that can be part of any existing application

 

Image 2 - Text Tool Configuration

Image 3 - Render tool Configuration

POC in action

• Let assume our 3rd application is located in www.alteryx.com - if the user selects 3rd app in the radio button

• Which would generate an Output Preview like below

Now If clicked on App 1, it would divert me to www.Alteryx.com

Keywords : Chained Applications, Chained Apps, Application Sequence, Skip Application Sequence, Branch Application Sequence, Application Order, Controlled Order, Trigger Next Application

Regards,

Maithreyan S

I love the ability to cache data. Sometimes, I've cached too far and I need to go back and alter a tool's configuration or make some other cache-destroying change. I then have to recache somewhere and sometimes the dataset is so huge it is a pain. I'd love to create multiple cache points as a safety or backup.

Currently, you can only type forward in the Description Window in the Meta Info tab.  So once your description is in there for your workflow, you have to retype the information or type it in notepad and save it back in there. It would be nice if you could type on any previous line in that window.

It would be nice to also have some additional fields that appear to be common among the community, such as Data Sources and Purpose.  That way you could use the Description window for version notes and any other notes for the user.

Hey team,

I like the profiling function in the browser. Unfortunately, there is not built-in export function. Would it be possible to implement a function to export the profiling results into excel and PDF?

Thanks,

Christoph

Hello all,

Here the issue : I have a workflow in my One Drive folder



In that workflow, I use a macro that writes a file with a relative path (..\6_Big_Data\EN\.csv ) :




Strangely, it doesn't work and the error message seems to relate to a folder that doesn't exist (but also, not the one I have set)

ErrorLink: Output Data (1): https://community.alteryx.com/t5/*/*/ta-p/724327?utm_source=designer&utm_medium=resultsgrid|Cannot access the folder C:\Users\saubert\OneDrive - Business & Decision\Documents\B&D_Market\6_Big_Data\EN\.

I really would like that to work :)

Best regards,

Simon

This is a question which is somehow in between Designer and Gallery ideas.

When saving a workflow to the Gallery, the user can select the Assets (elements which are also copied to the Gallery). The point in time during the save process is a bit questionable from my perspective.

Often, I develop workflows locally until they reach a state in which I want to move them to the Gallery so that they can be included in Schedules or be made available to other users. I would like to be able to select which macros or datafiles are copied to the Gallery as well much earlier in the development process. From my perspective, it would be great if the user could set the Assets settings in the "Workflow Dependencies" window as well. I propose 3 possible values for each element (macro or data file):

• "Auto" → decide on asset when saving the workflow to the Gallery (current behaviour)
• "Yes" → Copy this element as asset in the Gallery
• "No" → Do not copy this element to the Gallery 
• "N/A" → The question does not apply to this row (e.g., directory)

It could look like this:

When I open I'd workflow, I'd like the option click on "something" to see content previous created for the workflow.  The content I'd use most frequently is:  How was the INPUT data obtained?  ALL of the Alteryx workflows I will be creating with my current employer will require some level of pre-build of the data sources.  I would like to document the pre-build requirements (could be pages of text, so "comments" aren't optimal) and be able to ask for them as needed.

Optimally, this feature would accept .docx, .pdf and other standard formats.  Another option would be to support a URL that would link me to the content.  For my purposes, this would be even more advantageous as all of our knowledge content is on-line.

In short:
Add an option to cache the metadata for a particular tool so that it doesn't forget when using tool that have dynamic metadata such as batch macros or alteryx metadata engine can't resolve such as python tool.

Longer explanation:

The Problem:

One of the issues I often encounter when making dynamic workflows or ones that require calling external services is that Alteryx often forgets the metadata of what columns to expect. This causes the workflow to forget configuration of downstream tools when a workflow is first opened or when the metadata engine refreshes. There is currently the option to disable the metadata engine from automatically refreshing but this isn't a good option because you miss out on much of the value it brings.

Some of the common tools where I encounter this issue:

• Json parse
• Batch macros
• Python tool
• Regex parsing to rows

Solution:

Instead could we add an option to cache the metadata for a particular tool, this would save the metadata from the last time the workflow ran to within the workflows XML so that it persists when closed and reopened. Then when the metadata engine runs when it gets to this tool instead of resolving the metadata from the tool it instead uses the saved version in the XML. Obviously when it actually runs it would ignore this and any errors would still occur.

This could be an option in navigation pane of each tool. Mockup below:

This would make developing dynamic workflows far easier and resolve issues of configuration being lost when the metadata changes and alteryx forgets the options.

One of things I like to do is select a bunch of tools and to see the collective performance of particular part of a workflow. It would be super cool if these stats were aggregated. 

I could imagine then you could run alternative solutions side by side and then just select the tools involved to compare.

Maybe this pointless but my guess is that memory usage could be as important as processing time and is probably a simple addition to the performance profiling feature.

Currently, Cache and Run Workflow cannot be used if there's a second branch of data which goes around the tool which you want to cache. This slows down intermediate runs especially in complex workflows with a lot of inter-dependencies.

For example:

If you want to cache at the formula "Do something", Alteryx will not allow this because a single temporary cache file at this tool will not be sufficient:

My suggestion is that Alteryx allows multiple cache files for one single cache event. In this case:

Proposed process:

1. Run the cache run from the initial source(s) of data (here the Text Input tool) via all tools needed to produce the output of the selected tool (here Formula "Do something"). In this case: Text Input, left Select, Formula.
2. Produce a cache file for every tool which has a connection towards outside of the direct tool chain. In this case: Cache file 2 (as Alteryx does it today), Cache file 1 (new behaviour)

This way, I could use Cache and Run Workflow much more often which would save me a lot of time.