Alteryx Designer Desktop Ideas

One of the common issues when you build macros is the error "the schema of macro output XXX has changed between iterations"

So the next step that we commonly follow is to put a select tool into the flow just before the macro output - and convert all the fields to a specific type; untick the "unknown" field; and then sometimes have to go into the XML to add the "Forced = true" flag into the XML so that it doesn't change over time:

Please could you add an option under the "Options" tab to force / lock down the type of every field with one click?     That would eliminate dozens of clicks on every creation of a macro.

Thank you 

Sean

Currently if I drag a tool onto the canvas and it has multiple input anchors, Alteryx will try to connect to the first input anchor from the output of the nearest tool I am hovering near.

However the improvement I would like to see is where there are specific tools which are required to go into each input that it 'intelligently' connects to the correct input, for example on the gif below I have a PDF input and PDF template tool (pre-computer vision), and when I bring the image to text tool in, it will try and connect the output of the template tool into the D input anchor, when the correct input is the T anchor. What this leads to is me having to delete a connection and then re-wiring which slows down the development time.

Hi team,

Currently, we can FILTER results in the result window using some string operations like "String equals", "String Contains", etc.

Firstly, it's a great feature. Kudos for the same.

However, it would be really helpful if we can add the IN operator functionality to this Result window FILTER.

Most of the time, we always want to check for multiple values while filtering the data.

I am attaching a screenshot of the FILTER location that I am referring to!

For eg, In the above screenshot of the result window, I want to filter for Name IN ('Bullock County','Baldwin County','Butler County')

Kindly look into this.

Thanks in advance.

Regards,

Shreyansh Rathod

When creating annotations in the new image template tool as part of intelligence suite, a feature improvement would be the ability to modify the annotation, to change the dimensions of it.

Currently the only option is to cancel and redraw but being able to edit and drag the existing annotation would be a great addition. This is because the sizing and position of the annotation is important in the OCR process, and when there are many annotations on a page a user is likely to only need to make minor adjustments instead of deleting and redrawing. A mock up is below.

Hello all,

This is a very interesting feature of the List Box and Drop Down interface tool : the ability to select fields

However such a feature is not available for in-database, highly limiting the use of macros.

Please change.

Best regards,

Simon

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

I think the undo/redo capabilities in Alteryx could be greatly improved. Here is an idea that I think would be beneficial... 

I'd like to see which exact tools are affected by my undo/redo actions. An idea was suggested a couple years ago to move your location on the canvas, but that was not added to the roadmap. Instead, is it possible to add the tool ID to the undo menu so that it is obvious which tool each line is detailing?

This is the current debug menu that shows your previous actions:

When a tool is created, the ID can be displayed in this menu, but this is not shown when a change is made to an existing tool. My suggestion is that the menu would say:

4. Change Sort (3) Properties

This same change should be made in the Edit dropdown menu.

In order to make it easier to find workflow logs and be able to analyze them we would suggest some changes:

• In the log name instead something like "alteryx_log_1634921961_1.log" the log name should be the queue_id for example: "6164518183170000540ac1c5.log"

This would facilitate when trying to find the job logs.

 To facilitate reading the log we would suggest the following changes: 

1. Add the timestamp 
2. Add error level 

For the example of current and suggested log: 

 Please consult the document in attachment.

In the suggested format the log would be [TIMESTAMP] [ERRORLEVEL] [ELAPSEDTIME] [MESSAGE] 

The interactive results pane is great, but wouldn't it be cool if you could interact directly with the result pane to do things like filtering.

There are a few too many steps with the method at the moment, where you need to either copy the value or type it into the filter pop up. A simple right click and filter on selected value would be a big ux improvement.

With the new keyboard shortcuts in 2021.1, I would love to see this same functionality added to the global search. I would like for

1) The global search bar to be accessible via a keyboard shortcut

2) You can navigate through the results with the arrow keys and

3) I can click enter on a tool and it will add it to the canvas just like the tool palette now functions in 21.1.

cc: @A11yKyle 

Hello,

In cases where more than one field is being used in a join, the "Join (Tool ID) String fields can only be joined to other string fields" error message could be improved by indicating which field has a mismatch.

For example, if I'm joining Fields A, B, C, D... to fields Z, Y, X, W... in Join tool 24, and for some reason Field Z gets changed from String to Double, it'd be nice to see a message like:

"Join (24) (Field 1) String Fields can only be joined to other String fields"

or

"Join (24) String Fields can only be joined to other String fields (A)"

So that I know I need to go to a select tool and change the type of either A or Z.

Otherwise I look at the Join tool output and try to figure out which pair no longer has matching types, which can take a minute when dealing with a multiple-point join.

Thank you!

The Dynamic Input tool fails when attempting input a set of Excel files with the following error:

Error: Dynamic Input (1): The file "Test2.xlsx|||<List of Sheet Names>" has a different schema than the 1st file in the set.

Each spreadsheet contains two tabs and all tabs contain the same columns.

The root cause of the schema error is that maximum sheet name length in the two spreadsheets is different.  The first spreadsheet uses "East" and "West" for sheet names.  The second spreadsheet uses "North" and "South" for sheet names.  The Dynamic Input tool uses the longest sheet name when defining the effective Schema.

Excel limits sheet name length to 31 characters. It would be helpful if the Dynamic Input tool used 31 as the minimum string length when defining a schema from Excel sheet names.

The Input Data tool exhibits similar behavior when using a wildcard in the filename and the "Import only the list of sheet names" option.

A batch macro can be used as a workaround.

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,

It's nice to have this OpenAI Connector but it seems it must be the default OpenAI URL. In my company, we use OpenAI on an Azure instance and I'm unable to connect to it.

(by the way, I know pre-sales teams have developed lot of connectors for fireworks, mistral, etc.. it would be very cool to have it available).

Best regards,

Simon

Hello,

I think I have neer wrotten an easier idea : the tooltip for the run workflow button should indicate the keyboard shortcut (ctrl+R). So simple, so intuitive..



Best regards,

Simon

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

Hello all,

The reasons why I would the cadence to be back to quarter release :

-for customers, a quarter cadence means waiting less time to profit of the Alteryx new features so more value

-quarter cadence is now an industry standard on data software.

-the new situation of special cadence creates a lot of frustration. And frustration is pretty bad in business.

-for partners, the new situation means less customer upgrade opportunities, so less cash but also less contacts with customers.

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.

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