Alteryx Designer Desktop Ideas

XGboost regression is now the benchmark for every Kaggle competition and seems to consistently outperform random forest, spline regression, and all of the more basic models. For those of us using predictive modeling on a regular basis in our actual work, this tool would allow for a quick improvement in our model accuracy. And I think, from a marketing standpoint, having a core group of users competing in Kaggle using Alteryx would be a great way to show off Alteryx's power.

 

It is readily available as an R package: https://cran.r-project.org/web/packages/xgboost/index.html

Hi Alteryx Team,

My work is to create Output from Alteryx and upload the Output file into Tibco Spotfire. So i want a system in which Alteryx output directly goes in to the Tibco Spotfire and update Tibco Spotfire in every 6 hours.
So do you have any plan to connect the Alteryx with Tibco Spotfire? This is will help me to automate the project.
If not pls think on these concept for future use.

The Undo button in Alteryx has saved me many times! Unfortunately, I never know what all was "undone" when I click the button. It would be nice to update the Undo process in 2 ways:

• Replicate the Excel undo drop down (which includes a brief description of what will be undone and allows you to undo multiple actions at once).

• Move your location on the canvas to the area affected by the Undo-ing. Currently your location on the canvas doesn't change when you press Undo, even if the change being undone was off screen.

 

There is a need when visualizing in-Database workflows to be able to visualize sorted data. This sorting could be done 1 of 2 ways: In a browse tool, or as a stand-alone Sort tool. Either would address the need. Without such a tool being present, the only way to sort the data is to "Data Stream Out" and then visualize the data in Alteryx. However, this process violates the premise of the usefulness of the in-DB toolkit, which is to keep your data in-DB and process using the DB engine. Streaming out big data in order to add a sort is not efficient.

 

Granted, the in-DB processing doesn't care whether data is sorted or not. However, when attempting to find extreme values after an aggregation, or when trying to identify something as simple as whether null values are present in a field, then a sort becomes extremely useful, and a necessary tool for human consumption of data (regardless of the database's processing needs).

 

Thanks very much for hearing my idea!

Hi,

     I would like to see Global Variable being made available in Alteryx. I have seen the Global Constant being made available under Workflow "User" configuration. But this is constant and needs to be defined at Design time.

How about a Process Id that needs to be auto genearted and the same needs to be available across the formula tools used with in the workflow.

Configurable hotkeys/keyboard shortcuts would be awesome.  For instance, select/deselect highlighted fields or remove prefix are two commands that I use frequenctly but which are buried in menus.

Being able to assign hotkeys to favourite tools would be another time saver.  Imagine, ctrl-alt-F and a formula appears under the cursor!

Please remove all stopwords that help to identify the sentiment of a text. E.g. words like 'no' and 'not' are currently removed when you enable the 'remove stopwords' options. Here is an example:

 

 

 

People will probably use the option to remove stopwords without even thinking about issues like this and might remove relevant information from texts and then do a Sentiment Analysis afterwards and wonder why the results are bad.

 

Dear Alteryx, please find a better stopword list or remove some words from the list.

Speed up canvas edits - The Create/Remove Space Tool

 

Usually day two of working with a canvas I realize that I have been a fool, and I come up with a significantly more elegant or simple solution.  Moving all of the containers or tools to fit my slick new container is cumbersome and slow.  I've created a GIF of a feature several tools have which allows the user to easily move and arrange items on the canvas.

 

Open source tool used in demo: bpmnJs

 

 

 

 

 

 

I hope that there will be a radio button or a check box where Auto Save on Run can be disabled.  Auto Save on Run is a bad idea.  I often go into workflows and only need one report - so I break a bunch of connections to other reports, maybe I make some other small adhoc or one-off type changes and then Run the workflow.  I get my one, maybe modified, report and close without saving.  So the next time I open the workflow it's as it should be. 

 

With Auto Save on Run - I'd have to undo everything I changed.  What if it's not my workflow to be changing?  If there is no option to turn it off:  I'd have to make a copy of the workflow, open and make changes, then run, then close, then delete the workflow.

 

In general, you should never be saving unless it is a deliberate act performed by the user.

It would be great if you could create default settings for the Tool Containers. As workflows become larger, I use containers a lot. But once I have 10-15 containers, I have to set all of them to have a Transparency of 1 and a margin of None. While the changes don't take long to make, it would be nice if they could be preset.

I'm really liking the new assisted modelling capabilities released in 2020.2, but it should not error if the data contains: spatial, blob, date, datetime, or datetime types.

 

This is essentially telling the user to add an extra step of adding a select before the assisted modelling tool and then a join after the models. I think the tool should be able to read in and through these field types (especially dates) and just not use them in any of the modelling.

 

An even better enhancement would be to transform date as part of the assisted modelling into something usable for the modelling (season, month, day of week, etc.)

 

 

This is fairly simple/minor capability, but I do think it would save some time. Especially when developing back and forth between different layers of an Alteryx Environment.

 

Best,

dK

Currently zero-width spaces are not removed by the data cleanse tool. This means you can have two visually similar words like Dog and Dog but one is actually longer than the other due to zero width characters. The removal of these zero-width spaces can be added with the formula.

 

REGEX_Replace([_CurrentField_], "\x{200B}", "")

Hello,

I think it would be extremely useful to have a switch connector available in Alteryx. What I mean by a switch connector is a connecting line with an on/off state that will block the data stream through it when off. Something like below:


Switch Connector in an "Off" state

This would be extremely useful when you only want data to flow down some of the paths. In the example above, I might turn the switch connector to off because I want to see the Summarize results without outputting to a document.

The current methods for having a path/set of tools present but unused are insufficient for my needs. The two methods I and Alteryx support were able to find were:

One of the tools that I use the most is the SELECT tool because I normally get large data sets with fields that I won't be using for a specific analysis or with fields that need re-naming. In the same way, sometimes Alteryx will mark a field in a different type than the one I need (e.g. date field as string). That's when the SELECT comes in handy.

 

However, often times when dealing with multiple sources and having many SELECT tools on your canvas can make the workflow look a little "crowded". Not to mention adding extra tools that will need later explanation when presenting/sharing your canvas with others. That is why my suggestion is to give the CONNECTION tool "more power" by offering some of the functionality found in the SELECT tool.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For instance, if one of the most used features of the SELECT tool is to choose the fields that will move through the workflow, then may be we can make that feature available in the CONNECTION tool. Similarly, if one of the most used features (by Alteryx users) is to re-name fields or change the field type, then may be we can make that available in the CONNECTION tool as well.

 

 

At the end, developers can benefit from speeding up workflow development processes and end-users will benefit by having cleaner workflows presented to them, which always help to get the message across.

 

 

What do you guys think? Any of you feel the same? Leave your comments below.

Before Designer 2019.4 there was a "bug" in the workflow statistics collection that under the "SampleModule" data from the UsageGallery collection the name of the workflow run from within Designer was available.  We used that information to determine the common workflows run in our community as well as generating a measure of community growth.  The "bug" was removed in 2019.4 and now we can only determine the number of runs, but not the number of distinct workflows that were run.  This idea to do return the workflow name run to the information stored in the Mongo database.

 

 

Its definately not a good UX that the full browse is now in the output window.  I usually have my Output on autohide and its a few extra clicks to see the browses now... Can we have both the Browse Everywhere tab in Output and Configuration Panel?

A question has been coming up from several users at my workplace about allowing a column description to display in the Visual Query Builder instead of or along with the column name. 

 

The column names in our database are based on an older naming convention, and sometimes the names aren't that easy to understand. We do see that (if a column does have a column description in metadata) it shows when hovering over the particular column; however, the consensus is that we'd like to reverse this and have the column description displayed with the column name shown on hover. 

 

It would be a huge increase to efficiency and workflow development if this could be implemented.

I have often thought it would be nice to have a 'predicted run time' for a module calculated.

An adequate prediction might be the complete run time last time the module ran.  Then, in combination with a counter of how long a module has been running so far, we’d be well armed to estimate whether to go get a cup of coffee or not.