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

While In-db tools are very helpful and cut down the time needed to write complex SQL , there are some steps that are faster by directly writing SQL like window functions- OVER (PARTITION BY .....). In Alteryx, we need to create multiple joins and summaries to perform a window function. It would be immensely helpful if there was a SQL editor tool for in-db workflows where we can edit the SQL code at any point in the workflow, or even better, if they can add an "edit" function to every in-db tool where we can customize the SQL code generated and then send to the next tool.

 

This will cut down the time immensely and streamline the workflow to make Alteryx a true contender for the ETL solution space.

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.

Who needs a 1073741823 sized string anyways?  No one, or close enough to no one.  But, if you are creating some fancy new properties in the formula tool and just cranking along and then you see that your **bleep** data stream is 9G for nine rows of data you find yourself wondering what the hell is going on.  And then, you walk your way way down the workflow for a while finding slots where the default 1073741823 value got set, changing them to non-insane sized strings, and the your data flow is more like 64kb and your workflow runs in 3 seconds instead of 30 seconds.  

 

Please set the default value for formula tools to a non-insane value that won't be changed by default by 99.99999% of use cases.  Thank you.

 

 

With the release of 2018.3, cache has become an adhoc task. With complex workflow and multiple inputs we need a method to cache and save the cache selection by tool. Once the workflow runs after opening, the cache would be saved at the latest tool downstream.


This way we don't have to create adhoc cache steps and run the workflow 2X before realizing the time saving features of cache.

 

This would work similar to the cache feature in 11.0 but with enhanced functionality...the best of the old cache with the new cache intent.

 

Embed the cache option into tools.

 

Thanks!

When we create new workflows, we like to have them in our company template, to stnadardise documentation. This makes it easier for a supervisor to review, and for a colleague to pick up the workflow and understand what is going on. For instance, we have all data input on the left, and all error checks and workflow validation on the right, and a section at the top with the workflow name, project name, purpose etc. We have a workflow that we use as a template with containers, boxes and images all in the appropriate places

 

It would be great if there was an option to select a workflow as a template. When a new workflow is opened, it would load this template rather than having a blank canvas.

As a best practice, I'd like to automagically change any drive mapping to UNC when saving my workflows.  This applies to both local and gallery saves.

 

Cheers,

 

Mark

As a best practice, I'd like to automagically change any drive mapping to UNC when saving my workflows.  This applies to both local and gallery saves.

 

Cheers,

 

Mark

All the items in the 'View' menu have useful shortcuts. For instance, I'm always using Ctrl+Alt+D for the interface designer.

 

It would be nice to be able to quickly check workflow dependencies; at the moment there are far too many clicks to get there given the amount they are accessed (by myself and my colleagues at least...)

 

Quite often the window is only required briefly to check whether absolute/relative paths are used and to see inputs/outputs. It would really improve speed and ease of use if the window could be brought up with a couple of key strokes.

 

What are your thoughts?

When building and debugging batch macros - it is important to be able to add test values and use these for debugging. However, the input values in the interface tools section do not allow input, and the ability to save or load test values also does not work.

 

While there is a workaround - setting the values in the workflow variables - this does not work fully (it doesn't reflect in the interface view; and is incorrect in the debug report) and is inconsistent with all other macro types.

 

Please could you make this consistent with other ways of testing & debugging macros?

 

All screenshots and examples attached

 

Screenshot 1: not possible to capture test values

2018-12-26_10-55-16.jpg

 

Screenshot 2: saving and loading test values does not work

2018-12-26_10-56-39.jpg

 

 

Screenshot 3: Workaround by using workflow variables

Scree2018-12-26_11-00-45.jpg

 

Screenshot 4: Values entered do not reflect properly 

2018-12-26_11-03-01.jpg

 

 

Screenshot 5: Debug works partially

2018-12-26_11-05-37.jpg

 

 

All the items in the 'View' menu have useful shortcuts. For instance, I'm always using Ctrl+Alt+D for the interface designer.

 

It would be nice to be able to quickly check workflow dependencies; at the moment there are far too many clicks to get there given the amount they are accessed (by myself and my colleagues at least...)

 

Quite often the window is only required briefly to check whether absolute/relative paths are used and to see inputs/outputs. It would really improve speed and ease of use if the window could be brought up with a couple of key strokes.

 

What are your thoughts?

Hi, i am from ETL back ground and coming from my knowledge i would like to suggest or ask a feature which will helpful in alteryx solution.

 

"Error Line" : many ETL tools provide an "On Error" line which performs certain actions like "altering user by sending an email", "ignoring and going to next step" etc. It will be great if Alteryx can provide the same feature where we can have an error line (red line) for each tool.

 

Hope this is not a repeated idea. thank you for all the support and providing a wonderful tool.

 

Thanks,

Harika K

It would be awesome to default a container color depending on what tools you were using within that container. For instance:

 

Mostly input tools - container defaults to green

mostly prep tools - container defaults to blue

Mostly output/reporting tools - container defaults to orange

 

Along with this, it would be neat to be able to customize those colors depending on which tools mostly fill the container.

 

-AD

0 Stars

For whatever reason a schedule is disabled, whether a Studio expires, or for any other legitimate reason, a notification email should be sent to the Admin and the one that created the schedule in advance of it being disabled. When a scheduled workflow is not executed, it leaves us scrambling for answers. A sudden disablement of the schedule is disappointing to discover after all other stones have been turned. Notify us in advance of a schedule being disabled. 

0 Stars

When outputting to files in avro format, it would be nice to have Alteryx either throw an error/warning or automatically add a prefix when field names do not conform to the Apache Avro specifications. For example, if I were to try to output an .avro file with a field named "2018 actions", Alteryx could throw a warning/error to remind me to rename the field, or Alteryx could change the field name for me to something like "X2018_Actions".

0 Stars

Workflow Dependencies is a great feature. It would be even better if you can save several configurations so that you can switch between them with 1 click only, saving the effort to copy and paste. For example:

 

Configuration NameLocalTestProductionCustom
Dependency 1Path 1APath 1BPath 1C(Null)
Dependency 2Path 2APath 2BPath 2C(Null)
Dependency 3Path 3APath 3BPath 3C(Null)

 

 

Something similar to the Field Configuration (Field Type Files) for Select Tool.

 

Another option is you save several dependencies there so that you can choose them in the drop-down list of Input and Output tools.

 

This would facilitate sharing and deployment.

0 Stars

Designer should support statistical testing tools that ignore data distribution and support Statistical Learning methods.

 

Alteryx already supports resampling for predictive modeling with Cross-Validation.

 

Resampling tools for bootstrap and permutation tests (supporting with or without replacement) should be tools for analysts and data scientists alike that assess random variability in a statistic without needing to worry about the restrictions of the data's distribution, as is the case with many parametric tests, most commonly supported by the t-test Tool in Alteryx. With modern computing power the need for hundred-year-old statistical sampling testing is fading: the power to sample a data set thousands of times to compare results to random chance is much easier today.

 

The tool's results could include, like R, outputs of not only the results histogram but the associated Q-Q plot that visualizes the distribution of the data for the analyst. This would duplicate the Distribution Analysis tool somewhat, but the Q-Q plot is, to me, a major missing element in the simplest visualization of data. This tool could be very valuable in terms of feeding the A/B Test tools.

0 Stars

Hi there, I am looking for examples of financial modelling within Alteryx i.e. Discounted cashflow forecasting - Has anyone seen anything like this before? I've been through some Udemy Alteryx online training, but just can not figure out how to even use the NPV formula in Alteryx. Thanks!

0 Stars

When outputting to files in avro format, it would be nice to have Alteryx either throw an error/warning or automatically add a prefix when field names do not conform to the Apache Avro specifications. For example, if I were to try to output an .avro file with a field named "2018 actions", Alteryx could throw a warning/error to remind me to rename the field, or Alteryx could change the field name for me to something like "X2018_Actions".

0 Stars

I have a 1000 row excel workbook with multiple sections on the same sheet, each with a unique header. Each section has exactly 16 rows of data included. I want to pull the rows only from one specific header called "wages".

 

I tried using a multi-row formula and the below expression to pull only these 16 rows but it isnt working. Any ideas?

 

IF Contains([F1], "Wages", 1)

THEN [Row+1:Test]+1 & THEN [Row+2:Test]+1 & THEN [Row+3:Test]+1 & (... all the way to +16)

ELSE 0

ENDIF

0 Stars

Designer should support statistical testing tools that ignore data distribution and support Statistical Learning methods.

 

Alteryx already supports resampling for predictive modeling with Cross-Validation.

 

Resampling tools for bootstrap and permutation tests (supporting with or without replacement) should be tools for analysts and data scientists alike that assess random variability in a statistic without needing to worry about the restrictions of the data's distribution, as is the case with many parametric tests, most commonly supported by the t-test Tool in Alteryx. With modern computing power the need for hundred-year-old statistical sampling testing is fading: the power to sample a data set thousands of times to compare results to random chance is much easier today.

 

The tool's results could include, like R, outputs of not only the results histogram but the associated Q-Q plot that visualizes the distribution of the data for the analyst. This would duplicate the Distribution Analysis tool somewhat, but the Q-Q plot is, to me, a major missing element in the simplest visualization of data. This tool could be very valuable in terms of feeding the A/B Test tools.

Top Starred Authors