community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the star in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

Alteryx has different behaviours for conversion errors depending on the type of conversion desired. When converting from string to date data type, a conversion error will generate a NULL value. When converting from a string to a numeric data type, a conversion error will generate 0. Why the different behaviours? There is a lack of harmony here. 0 is a valid value and should not be the generated value for a failed string to numeric conversion. It should be NULL.

 

When I perform data type conversions, i do not apply them directly to the source field and then cast it. If there is a conversion error, then I have lost or corrupted the source information. Rather, I create a target field with the desired data type and use a formula to apply a conversion, such as datetimeparse or tonumber. Finally, I do a comparison of the source and target values. If the datetimeparse generated a NULL then I can PROGRAMMATICALLY address it in the workflow by flagging or doing some other logic. This isn't so easy to do with numerics because of the generated 0 value. If I compare a string "arbitrary" to the generated 0 value as a string then clearly these do not match. However, if I compare a scientific value in a string to the converted numeric as a string, then these do not match though they should. My test of the conversion shows a false positive.

 

I want a unified and harmonised conversion behaviour. If the conversion fails, generate a NULL across the board please. If I am missing something here and people actually like conversion errors to generate 0 please let me know.

There are a several ways to store the Avro schema in Hive:

 

  1. Literal JSON string stored in the Hive table properties (Alteryx currently supports)
  2. Reference to the schema file stored elsewhere
  3. Pass in the schema as a run-time property in Hive

Alteryx only supports Option #1, but that runs into a 4000 Character Limitation which is the default schema limit in Hive’s internal DB. Is it possible to have Alteryx support the other two options to be able to support data sets with large schema definitions?

Probably more of a bug. Not sure if this annoyes anyone else, but when a running workflow in a different tab completes, the current windows focus is gone, even you have the pop-up notification disabled. Check the video and see what happens at 0:11 when tab 105 finishes running while I'm typing a super complicated code Smiley Wink

 

I've had several of my users complaining about the Visual Query Builder view after the last couple of releases. When you maximize the window, half of the screen is taken up by blank gray space and there is no way to adjust it and it's very difficult for those who do not know SQL to build their queries in this very small white space. Need to be able to adjust the gray space.

 

 

visual query builder.jpg

When you enable SAML authentication for Alteryx Server it does allow Single Sign IN but it does not support Sign OUT. This means that after you close your browser the session remains active. If the browser is opened again and the Gallery page is loaded it will pick up the session that was activated before instead of creating a new session. At the very least a session time out limit should be added.

  • Defect

I've had several of my users complaining about the Visual Query Builder view after the last couple of releases. When you maximize the window, half of the screen is taken up by blank gray space and there is no way to adjust it and it's very difficult for those who do not know SQL to build their queries in this very small white space. Need to be able to adjust the gray space.

 

 

visual query builder.jpg

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

  • Defect

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

  • Defect

It would be awesome if there was a cross tab in DB option because right now I have to stream out millions of records to build a cross tab.

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

Probably more of a bug. Not sure if this annoyes anyone else, but when a running workflow in a different tab completes, the current windows focus is gone, even you have the pop-up notification disabled. Check the video and see what happens at 0:11 when tab 105 finishes running while I'm typing a super complicated code Smiley Wink

 

This appears to be a bug with either the Layout Tool or the Render Tool. When I setup two Tables using the Horizontal Layout Tool and export to Excel using the Render tool, the font size of the bottom-right cell of the first table is too large. No amount of changing the font properties within the Alteryx Reporting tools appears to fix this.

 

BugExample1.png

Despite being an Alteryx user for 2 and a 1/2 years this is something I have only recently came across but it does not appear that you are able to use debug mode appropriately with macros.

What I mean is, I have a macro input which drives a series of drop down boxes. In debug mode my drop down boxes will not populate. Now I understand why, Alteryx doesn't know what the input is so it doesn't generate the meta data for the debug mode drop downs.

What I suggest Alteryx do is automatically convert your macro inputs for file browses for the purpose of debug mode (I had to do this myself manually and it was a tedious task, not only to set up but then maintain two separate versions, one essentially an application and one a macro).

Or, by default debug mode uses the macro input data to run through debug mode as.

Ben

There are a several ways to store the Avro schema in Hive:

 

  1. Literal JSON string stored in the Hive table properties (Alteryx currently supports)
  2. Reference to the schema file stored elsewhere
  3. Pass in the schema as a run-time property in Hive

Alteryx only supports Option #1, but that runs into a 4000 Character Limitation which is the default schema limit in Hive’s internal DB. Is it possible to have Alteryx support the other two options to be able to support data sets with large schema definitions?

If you have a field length of say 10 in a Select Tool, then you use a Left Join tool and change that length to say 4. This turns that field red - as it should.  Then add a Select tool after the Union.  It should say 4 in the second Select tool.  But instead it says 10.  If it was changed to 10 (and it wasn't) then the field s/b red.

Despite being an Alteryx user for 2 and a 1/2 years this is something I have only recently came across but it does not appear that you are able to use debug mode appropriately with macros.

What I mean is, I have a macro input which drives a series of drop down boxes. In debug mode my drop down boxes will not populate. Now I understand why, Alteryx doesn't know what the input is so it doesn't generate the meta data for the debug mode drop downs.

What I suggest Alteryx do is automatically convert your macro inputs for file browses for the purpose of debug mode (I had to do this myself manually and it was a tedious task, not only to set up but then maintain two separate versions, one essentially an application and one a macro).

Or, by default debug mode uses the macro input data to run through debug mode as.

Ben

As the title indicates, the Alteryx POW() function in the formula tool returns null when you ask for the odd root of a negative number. Either I am making an error or this is a bug.

 

negative_root.PNG

  • Defect

This appears to be a bug with either the Layout Tool or the Render Tool. When I setup two Tables using the Horizontal Layout Tool and export to Excel using the Render tool, the font size of the bottom-right cell of the first table is too large. No amount of changing the font properties within the Alteryx Reporting tools appears to fix this.

 

BugExample1.png

I decided to get real fancy when building a standard macro the other day. I checked the box on my macro input that made the connection optional:Capture2.PNG

 

shocked-will-smith

 

It worked really well. My macro then became more complex, so I changed it to a batch macro. To my great surpise/astonishment/shock, the optional incoming connection is no longer optional:

Capture.PNG

 

The standard macro is working as expected on the left, but the batch macro is producing an error because my optional connection is requiring that something be connected to it.

what-did-you-just-say

 

I've been told that the code to make it optional is not there for batch macros and that this would be a product feature/improvement.

 

Problem:

Currently, the scheduling via designer controller is independent of the gallery. So, even after a canvas is deleted, the scheduler still continues to execute the cached version of the canvas, as long as the scheduler exists.

Note, this issue does not occur when the canvas is directly scheduled in the gallery, and only occurs when you schedule via the Designer on the controller directly.

 

Steps to replicate issue:

1) Publish a canvas into gallery

2)Schedule the canvas to run daily via the Designer --> Options --> View Schedules --> Select Controller --> Create new workflow and schedule

3) Delete the canvas from gallery

4) You will notice that the canvas is still getting run on the defined schedule, even though you have deleted the canvas

 

Observed in Alteryx 11.5.1

 

Idea Recommendation:

Golden copy of a canvas should be the version existing in the gallery. Once the gallery instance of the canvas is deleted/replaced with a new version,

  • All related artifacts to the old version should be marked as "Deleted"
  • All existing schedules should be stopped from being executed
  • We should continue to retain all meta data attributes and execution history related to the old version (should not be wiped out) but clearly marked as archived/deleted

 

@SeanAdams @LizaNemchynova

 

Top Starred Authors