The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

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 */

 

2024-02-21 08_18_04-Alteryx Designer x64 - _New Workflow1.png

  

2024-02-21 08_18_11-Alteryx Designer x64 - _New Workflow1.png

0 Likes

Writing to XLSB Files using Delete and Append does not behave properly.

 

Alteryx currently is having an issue with writing to an XLSB file using the Delete and append option with Take the file/table name From field.

 

Issue:

  • Old data gets deleted, and new data is added but on the wrong row.
  • New data is added after location where old data was originally.
  • This output error for XLSB files only shows when using Take the file/table name From field. Static paths are fine.

Workaround:

Create a Batch macro to simulate the Take the file/table name From field function without actually using it.

 

Example of Issue:

 

Record IDOriginal File---->Updated File
1Old Data----> 
2Old Data----> 
3Old Data----> 
Old Data----> 
1200Old Data----> 
1201 ---->New Data
1202 ---->New Data
1203 ---->New Data
 ---->New Data

 

0 Likes

I received a "string variable switched type" error on the filter tool performing a basic filter on the value column of "is not empty" after a transpose tool.  The value column is datatype of  V_String 255.  So even though the values are null, blank, number, text, it is all string as per the data type column flowing in.  When switching from basic to custom with formula: IsEmpty([value]) same error.   BUT, when using the Formula Tool to generate a new column for true/false there is no error. Also the Fitler Tool works as expected with IsNull on this dataset.

 

Please look into the isEmpty code in the Filter tool so that it behaves correctly.

 

Please note that pre-splitting the data with the isEmpty flag column using the formula tool, applying IsEmpty Basic Filter  to the True and To the False both worked without incident.  

 

What would be nice is if there is an error in the filter tool that it would output those to it's own stream.  Something like - True (T), False (F), Error (E).

Basic Filter Error.png

Add Unicode category to the cleansing tool

Hi currently if you use the cross tab tool and the names of the new fields should have special characters they end up being replaced in the new headers with underscores "_", and then need to be updated in someway. It would be great if this was all done in the tool. In other words the new headers have the special characters as desired

0 Likes

Alteryx is great for for forecasting but it would be useful if we could use it for back casting (predicting historically). Might have fewer use cases than forecasting but would still be useful.

0 Likes

Hey it would be great if we could use alteryx designer on macs (without needing to use VDIs or splitting the hard drive)

0 Likes

Hello all,

As of today, the error message when trying to activate a license doesn't give any useful information :

 

image.png


I want to know :
-do I manage to access to the Alteryx Licensing? (so maybe a security/proxy issue.. so I have to contact my IT)
edit : for that there is another message usually

 

whitelist.png


-is the key correct but not more seats? (so I have to contact the Alteryx License manager) Or another issue?
Here, I perfectly know the license key is correct so the error message is really misleading.
-also displaying the machine id as it appears on the License portal would help.
-and anything that can be helpful to debug.

Best regards,

Simon

I know that the container title/label should or can be short, and as much descriptive as possible. Also, adding extra comments inside the box helps to a more detailed explanation on regards what process is run inside the container. Visually, if I collapse the container, the "Short" title given can't be of much help.

Could it be possible to enhance the "caption" for the "Container" title? I mean to allow to type 2, 3 or more lines of text?. This will make the Container title more descriptive and visually will allow to have the containers collapsed but with a reasonable amount of text that describe (as much as possible) what happens inside the container.

 

At the moment, If I type certain amount of text, the container expands according to the length of the text 

 

Below is the typical container Title 

Normal Container Title.JPG

 

 

Below is the current situation if a person would like to give a bit of more description in the "Container" header (The container expands)

 

Extra Text in Container_CurrentProblem.JPG

 

An dream would be to have the workflow with all containers collapsed and with titles that tell you what they do (see image below)

 

 Ideal Alteryx Containe.JPG

 

  • Enhancement
0 Likes

I am using Alteryx as an ETL Tool and then QlikSense for data visualization.

Alteryx only gives QVX outputs which are the old version QlikView files. It works for QlikSense but it slows down the system. So, the QlikSense support suggested using QVD outputs. 

I want to suggest supporting QVD files as QlikSense is being used more widely instead of QlikView, most users are migrating to QlikSense.

It would be more useful and efficient if Alteryx supports latest file format.

Hello all,

It's really frustrating to have an "alteryx field type" in In-Database Select. It doesn't even make sense since we're manipulating only data in SQL database where those types does not exist. What we should see is the SQL field type.
alteryx_monetdb2_.png
Best regards,

Simon

We have lots of tools that create new column(s) from the Inputs, e.g., Generate Rows. It'd be very nice if the new column(s) is/are highlighted in the Output. This makes it a lot easier for users when developing the workflow.

  • Enhancement

Good morning!

 

This may be a very simple thing, but would it be possible to add a DateTimeQuarter() function? We have DateTime Second, Minute, Day, Month, and Year, and being able to have an easy formula for the quarter as well would be incredibly convenient. 

 

Thanks,

Kat

Sometimes, Control Containers produce error messages even if they are deactivated by feeding an empty table into their input connection.

 

screenshot_error_in_spite_control_container_deactivated.png

(Note that this is a made up example of something which can happen if input tables might be from different sources and have different columns so that they need separated treatment.)

 

According to the product team, this is expected behaviour since a selection does not allow zero columns selected. This might be true (which I doubt a bit), but it is at least counter-intuitive. If this behaviour cannot be avoided in total, I have a proposal which would improve the user experience without changing the entire workflow validation logic.

(The support engineer understands the point and has raised a defect.)

 

Instead of writing messages inside Control Containers directly to the log output (on screen, in logfile) and to mark the workflow as erroneous, I propose to introduce a message (message, warning, error) stack for tools inside Control Containers:

  1. When the configuration validation is executed:
    1. Messages (messages, warnings, errors) produced outside of Control Containers are output to the screen log and to the log files (as today).
    2. Messages (messages, warning, errors) produced inside of Control Containers are not yet output but stored in a message stack.
  2. At the moment when it is decided whether a Control container is activated or deactivated:
    1. If Control Container activated: Write the previously stored message stack for this Control Container to the screen and to the log output, and increase error and warning counts accordingly.
    2. If Control Container deactivated: Delete the message stack for this Control Container (w/o reporting anything to the log and w/o increasing error and warning count).

This would result in a different sequence of messages than today (because everything inside activated Control Containers would be reported later than today). Since there’s no logical order of messages anyways, this would not matter. And it would avoid the apparently illogical case that deactivated Control Containers produce errors.

Currently when debug mode is entered in analytic apps and macros, the direct inputs to the app/macro when the error occurred are hardcoded into a workflow in debug mode, so that errors can be more easily detected.

 

However, inputs into analytic apps also create global variables which can be used in the more code-heavy aspects of Alteryx such as the Formula Tool. These are not updated in the same way which can cause workflows to break in debug mode - it would be really helpful if global variables could be updated in the same way as the inputs into tools are.

Everyone knows the importance of adding the appropriate controls and governance to your workflows - and often, this means including events that will generate notifications if a workflow is running with errors.

 

But who is the audience of that email? If it's not a developer, will that person know what they are reading and where to focus?

 

How about a developer that would like to customize the message that the end user will receive?

 

Porting some existing functionality from other tools in the Alteryx toolkit to the Events page could easily provide added flexibility to event generation:

 

1) Add a formatting bar to the tool like shown in the image below

-- Style changes

-- Alignment

-- Highlighting

-- Coloring

-- Images

 

2) Add a function bar to the tool like shown in the image below

-- Ability to view all available variables

-- Ability to apply formulas using variables

-- Ability to save formulas

 

Events.JPG

 

What do you think? Give this post a thumbs up if you find the post helpful!

  • Enhancement

It would be great if we could add example workflows to our macros, accessible in the same way as from the original tools (example hyperlink shown after single-clicking on a tool in the tool palette or when searching in the search bar).

 

There is a post on how to do it for custom tools How to add an example link in the custom tool (alteryx.com). The way described there has limitations and does not seem to work on macros: I was able to get the link to show up, but nothing happens when I click.

 

My suggestion, make it easy to add an example workflow to a macro, like it is to change the logo or add a help link.

example workflow.png

Hello all,


As of today, we use the good old alias in-memory to connect to our datasources in in-memory. We have several environments so we use constants in order to change the name of the in-memory alias during execution.

To illustrate :

simonaubert_bd_0-1701895804110.png

 

 

Depending of the environment, the constant « v_gp_contexte » will take different values :

  • GP_DS08_SIDATA for la dev.
  • GP_EE_SIDATA for prod.

Sounds nice, right? But now, we would like to use DCM and the nightmare begins :

We can't manually change the name and set the question :

simonaubert_bd_2-1701895988262.png

 

if we look at the xml of the workflow, we only find an id so editing it is useless :

simonaubert_bd_3-1701895988262.png

 


(for informationDCM connections are stored in some sqlite db in C:\Users\{yourname}\AppData\Local\Alteryx

So, I would like to use the DCM inside the in-memory alias (the in-memory alias is stored and can be edited), just like for in-db connection alias.

Best regards,

Simon

 

 

Hi - Please delete this if it perhaps exists already in a newer version.  (I am on 2022.1 and don't see this functionality.) 

 

I would love to see the ability to right click a tool that isn't in a container and be able to add it to an existing container.  Currently I drag it over and drop it into the container then move it back to where it was.  Inevitably I misalign the tools and spend time getting it linear again. It would be cool if based upon the choice made in the right click, it would bring the assigned container around the tool in its existing location.

 

OR

 

Perhaps within the config of the container you could choose tool #s to add to the container?

 

Anyways this isn't a huge need but it would be nice to see that additional functionality for people that spend a disproportionate amount of time aligning and distributing their tools HORIZONTALLY.  (Nobody cares about the people that do vertical workflows.)

 

 

container idea.png

 

 

 

 

Please consider implementing a consistent case-sensitive option for all tools and functions.

 

To compare string values, including case-sensitivity:   This post had a good description of the challenge, but the post has been archived:

   https://community.alteryx.com/t5/Alteryx-Designer-Discussions/IF-equation-ignoring-case-BUG/m-p/4170...

   For all the time I've used Alteryx, I thought that IF "test" = "TEST" would evaluate to false. Today I realised that isn't the case and I was surprised. I'm very surprised that "equals" performs like it does.

 

A few existing Ideas request case-sensitivity for individual tools:

   Case insensitive option while joining two data sets
   https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Case-insensitive-option-while-joinin...

 

   Unique tool enhancement - deal with case sensitive data
   https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Unique-tool-enhancement-deal-with-ca...

 

 

This new Idea requests system-wide consideration for case-sensitivity, for all tools and functions.

 

Current state:

 

These tools and functions are case-sensitive:

  • Tool: Join
  • Tool: Tile
  • Function: FindString
  • Functions: MD5_ASCII, MD5_UNICODE, MD5_UTF8

These tools and functions are NOT case-sensitive:

  • Tool: Unique
  • Function: CompareDictionary

These tools and functions can be either case-sensitive or NOT case-sensitive, depending on the options used:

  • Function: Contains
  • Function: EndsWith
  • Function: StartsWith
  • Functions: REGEX_Match, REGEX_Replace, REGEX_CountMatches

Current Challenges:

   How do we easily identify Lower Case, Upper Case, Mixed Case?

   How do we easily compare strings for equality, using case sensitivity?

 

Request:

   Ensure all tools and functions include an option to ignore or consider Case

   Create new functions for IsUpperCase, IsLowerCase, IsMixedCase

   Create a new function for IsEqual, with an option to ignore or consider Case

 

See attached workflow, which

  • uses REGEX_Match to create 3 new fields: IsUpperCase, IsLowerCase, IsMixedCase
  • creates a field [Flag: Original value IsEqual, case-sensitive], to compare strings for equality, using case sensitivity

 

Top Liked Authors