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.
It would be useful to be able to select a single container (containing a data input) or multiple containers using Shift, and run those and only those.
When building a new element to a larger workflow, I often enter a new Input in a new container, the ability to run just that container without having to turn off all my other containers would be really useful in speeding up the start of joining things together.
When I use the Comment Tool its difficult to select the tools inside it, but when I use the Container Tool the Container Text doesn't support Font Sizes, and doesn't support multiple lines of text so I end up moving the Comment into the Container, but still have problems selecting a group of tools.
So a combined Comment and Container Tools would be wonderful!
Bonus: If the Comment Tool could support Multiple Font Sizes.
I'm not sure if this will ever be possible, but I know that it would greatly benefit me and I'm sure thousands of other users. In my work place I am constantly working in a conference room and at my desk. At my desk I am wired into an Ethernet connection while in the conference room I am wireless. When I start my workflows after working with my team in the conference room, I can't go back to my desk until the workflow is finished running because I am changing internet connections and I lose connection to the databases. With the pause button it would become possible to run a workflow and then change my internet without losing connection to the databases.
Another use for this would be while testing a workflow with a new tool. There are times I run a workflow that can take a few hours, but then I realize there is a mistake somewhere in my workflow, where the data hasn't reached yet. I think it would be very helpful to be able to pause the workflow and add the new tool in, while seeing results from tools it has already passed through.
But yet again this is just an idea that relates to me, I wonder what the rest of the community thinks.
Often as I am scraping web sites, some clever developer has put an invisible character (ASCII or Unicode) in the data which causes terrible trouble.
I've identified 89 instances of zero-width or non-zero-width glyphs that are not visible and/or Alteryx does not classify as whitespace. There are probably more, but Unicode is big y'all.
Unfortunately, the Trim() string function only removes 4 of these characters (Tab, Newline, Carriage Feed, and Space). REGEX_REPLACE with the \s option (which is what the Cleanse macro uses) is a little better but still only removes 20. And it removes all instances, not just leading and trailing.
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.
At the moment containers either expand and overlap other tools, or you have to leave space for them (defeating the original purpose of using them). Is there a way we can have the containers expansion shift the workflow so the others tools shift down / right to account for this expanision?
This functionality won't be mission-critical to anyone, I'm sure, but a lot of IDEs and upgraded text editors (lookin' at you Notepad++) have the ability to customize the colors of text, the background, and other various tabs/objects that may appear on the screen. I understand that this is more important for code-based systems where the coloring improves readability so much, but I thought it might be a neat feature. I think leaving the tool colors standardized is a good idea though, just the canvas and outerlying windows. It could include the colors for the formula syntax highlighting too?
The icing on the cake would be the ability to save and share your settings or create a repository for them in the public gallery or something.
The DateTime tool is a great way to convert various string arrangements into a Date/Time field type. However, this tool has two simple, but annoying, shortcomings :
Convert Multiple Fields: Each DateTime tool only lets you convert one field. Many Alteryx tools (MultiField, Auto Field, etc.) allow you to choose what field(s) are affected by the tool. If I have a database with a large number of string fields all with the same format (such as MM/DD/YYYY), I should be able to use one DateTime tool to convert them all!
Overwrite Existing Field: The DateTime tool always creates a new field that contains your converted date/time. I ALWAYS have to delete the original string field that was converted and rename the newly created date/time field to match the original string field's name. A simple checkbox (like the "output imputed values as a separate field" checkbox in the Imputation tool) could give the flexibility of choosing to have a separate field (like how it is now) or overwrite the string field with the converted date/time field (keeping the name the same).
Alteryx is overall an amazing data blending software. I recognize that both of these shortcomings can be worked around with combinations of other Alteryx tools (or LOTS of DateTime tools), but the simplicity of these missing features demonstrates to me that this data blending tool is not sufficiently developed. These enhancements can greatly improve the efficiency of date handling in Alteryx.
STAR this post if you dislike the inflexibility of the DateTime tool! Thank you!
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.
We've had several requests from clients for the ability to import password protected Excel spreadsheets into Alteryx. Within Alteryx, it would be good to specify the password and inport the file without the need to create an unprotected copy for use in Alteryx.
Now that the formula tool has syntaxing and highlighting and autofilling, it would be great if it would color things differently depending on the datatype. Currently fields are blue and constants are green when I go to select them:
I think the constants can remain green, but then maybe have something like: strings = blue, numbers=red, dates=orange, blobs/spatials/bool/anything else=black (or any other colors that look good). Then the formula tool would also have similar colors. Currently my fields and constants both look purplish:
Instead, I think the colors should remain the same (ie. ALAE Reserve should be blue and the engine should be green)
The default data type for new columns used to be Double, and now it is V_WString. Is this user-configurable? I find that, at least in my work, needing a formula to output a Double is way more common than a V_WString. I'm curious of other community members' thoughts here. If there isn't a consensus, it would be great to have this be a user-configurable default.
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.