This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Could we please have a Type field added to the "Select Fields to Cleanse" configuration window for the Data Cleansing Tool? This small feature would save a lot of time (saving the time needed to check the Metadata for every field every time I use the Data Cleansing Tool). Similar functionality to the way the Summarize Tool displays both Field and Type (just one additional field).
Pardon my sad photoshopping 🙂
Note: I realize the Data Cleansing is a macro and this functionality is not currently available with the "Check Box" interface tool.
Alteryx Server was recently updated to allow TLS-mediated connections to the MongoDB persistence layer. This allowed us to switch off of the embedded MongoDB to a highly-available MongoDB Atlas cluster. To our surprise after the switch, when we went to edit our workflows that make use of the persistence layer's data (Server Usage Report, etc.) to hit the new Atlas cluster, we found that the MongoDB Input tool does not support TLS connections. This absolutely needs to be changed. Based on organizational constraints, Atlas is our only option for a HA persistence layer. We absolutely have to have TLS support for the MongoDB Input tool. There is no other way for us to natively query our server persistence layer in Designer. Please bring the MongoDB Input tool into alignment with the MongoDB connections that are supported by Alteryx Server.
I've just downloaded the latest version, 2020.2.3, which I do like overall. However, I was horrified to see an issue that keeps coming back, I'm hoping this time it doesn't take as long to fix. I'm referring to the Select tool no longer showing the whole (or at least the majority) of the field name...again (this is at least the 3rd time this has come back). It appears you only show the first 6-9 characters making it so I have to hover my mouse over each column to get the full name or drag the field pane out every time I click on a select tool/join tool/spatial match tool/find nearest tool/etc etc.
I suggested in the past each time this has happened before, that you just drop the description field, which you give the most room to by far. I've been using Alteryx since you were SRC (too depressing to count how many years that's been...so old) and I have not once put anything in the description area, does anyone really ever use this area on a consistent basis? Or if you can't drop it, maybe not allocate all the room to it & make it one of the smaller panes, which would allow for the actual field names to have more display room, which then allows your user base to more easily tell what is in the data they just loaded.
This is definitely a step backwards in my mind in design/time efficiency, holding out hope this was an oversight & will be fixed next release (fingers crossed, rabbit foot rubbed, lucky shirt on, donated to charity, & knocked on wood)! Please please please.
This has probably been mentioned before, but in case it hasn't....
The dynamic input tool is useful for bringing in multiple files / tabs, but quickly stops being fit for purpose if schemas / fields differ even slightly. The common solution is to then use a dynamic input tool inside a batch macro and set this macro to 'Auto Configure by Name', so that it waits for all files to be run and then can output knowing what it has received.
It's a pain to create these batch macros for relatively straightforward and regular processes - would it be possible to have this 'Auto Configure by Name' as an option directly in the dynamic input tool, relieving the need for a batch macro?
This has probably been mentioned before, but in case it hasn't....
Right now, if the dynamic input tool skips a file (which it often does!) it just appears as a warning and continues processing. Whilst this is still useful to continue processing, could it be built as an option in the tool to select a 'error if files are skipped'?
Right now it is either easy to miss this is happening, or in production / on server you may want this process to be stopped.
The crosstab tool replaces any non-alphanumeric characters with underscores in column names. It would be helpful to keep the original values as column names (or to have the option to toggle whether or not special characters are replaced with underscores).
This is often an issue for reporting and for dynamically-populated app inputs (e.g. drop-down), where we need to retain the special characters.
For example, say I have the following dataset:
Currently, the crosstab tool produces this:
I would like this:
There are currently (somewhat cumbersome) workarounds such as adding an extra row with the original names, and then using Dynamic Rename to rename the columns, but it would be great to be able to use the data straight out of the crosstab!
I often need to create a record ID that automatically increments but grouped by a specific field. I currently do it using the Multi-Row Formula tool doing [Field-1:ID]+1 because there is no group by option in the Record ID tool.
Also, sometimes I need to start at 0 but the Multi-Row Formula tool doesn't allow this so I have to use a Formula tool right after to subtract 1.
So adding a group by option to the Record ID tool would allow the user not to use the multi-row formula to do this and to start at any value wanted.
I personally think it would work better to tab from 'Select Column' to 'Enter Expression Here' and not the 'Functions' List as probably people who are tabbing would immediately like to start typing the formula rather than going through functions, fields, etc.
When writing an expression in a Formula tool, I love that you can just type an open bracket and suggestions pop up that allow you to auto-fill the rest of the variable name. What I find frustrating, however, is that once you type the open bracket, the highlighted field automatically moves to the one where your mouse is pointing, regardless of if you have moved your mouse or not. I think it makes more sense to always highlight the first field in the list and only take mouse position into account once it has actually moved.
It is hard to describe in just a picture as opposed to a video but essentially I had my mouse below where I was typing in the screenshot below then when I typed the open bracket, the 3rd field listed automatically got selected even though I never moved my mouse.
Sometimes, as a sanity check, I would like to be able to model only the mean of my data set, i.e. I would like to use a predictive tool with no predictors included. The result would be a model with only an intercept, and this value would be the mean of the target variable. This would not be an important feature for final models, of course, but when starting to look at a data set and build up a model, it can be useful to first ensure the model is producing the expected output in the simplest case.
Note, this can be achieved when just one predictor is included, but it takes some math (see below), so it would be nice to be able to have this as a built-in option.
The expression editor in the RegEx tool is only a single line, which makes it really hard to edit long regular expressions. See attached photo comparing the expression editor in the RegEx tool compared to the formula tool for the same expression. Please make the RegEx editor box either wrap to multiple lines, have a pop-out expression editor, or something so we can see long expressions.
The select tool does a great job at flagging up when something has changed from its original state. However why does this not happen with the checkboxes to keep or remove a field? It would be much faster and easier to read if we could have the same color conditional formatting as the rest.
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.)
With the new intelligence suite there is a much higher use of blob files and we would like to be able to input them as a regular input instead of having to use non- standard tools like Image, report text or a combination of directory/blob or input/download to pull in images, etc. I would like to see the standard input tool capable of bringing in blob files as well.