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.
When writing a good amount of code, it is easy to get lost in a sea of parentheses. Just when you think you're all done, you get an error that can force you to scour through your code to find the missing, extra, or misplaced parenthesis.
A common feature today is to highlight a parenthesis when its partner is clicked on. This instantly lets you know if you have the wrong number of them and where.
I didn't think this was that important early on in Alteryx, at least for me. Formulas were meant to be short and easily readable at a glance. Now as I dig deeper, there's R, Python, SQL and other text-heavy inputs.
I don't need a full-fledged text editor in Alteryx, but I would love some quality of life features like parentheses matching.
With the 2019.3 release the summarize tool now includes prefixes for grouped fields. While a nice addition, in application it makes using this data downstream (like joining to other tables) more involved because of needing to remove this prefix.
It would be nice to have this as an option (a checkbox to add/remove prefixes maybe) or just revert back to pre-2019.3 behavior...thanks!
When training people on the use of action tools, something that I always have to hit on is that when you are telling the tool which piece of the XML that you are adjusting, it's sort of difficult to tell what you have selected, and super easy to accidentally select something else.
When you initially select the action to take it's this nice Blue Color. However, it still doesn't feel exactly like you have actually selected anything or told the Action Tool what to do, since it's so easy to just select any other one of these actions.
A slightly different problem is that if you are selecting an action that has been previously configured, it is just this light grey color. So it can be easy to accidentally change your settings because you may not realize it's actually set up.
Here is a recent community post that sort of outlines a few of these problems.
We need color coding in the SQL Editor Window for input tools. We are always having to pull our code out of there and copy it into a Teradata window so it is easier to ready/trouble shoot. This would save us some time and some hassle and would improve the Alteryx user experience. ( I think you've used a couple of my ideas already. This one is a good one too. )
I would like to see more files types supported to be able to be dragged from a folder onto a workflow. More precisely a .txt and a .dat file. This will greatly help my team and I do be able to analyze new and unknown data files that we receive on a daily basis.
Please can you fix the copy and paste of renames across field. It's a behavior that I see in many tool's grids and drives me mad. Its not just select.
Take the attached screen shot. In the select tool, i've renamed "test 2" to "rename2". Fine it works. No issue.
I then copy rename2 and paste into the test3 field, and it copys the entire row's data (and metadata) into that little box, tabs, spaces the lot. I end up with something like the screenshot. Really not sure it was meant to be designed this way, as I cant really see the point.
Alteryx does not currently have to email tool that is configurable to use SMTP Authentication for Microsoft Office 365 or any server requiring authentication. Our office printer can authenticate over SMTP and with TLS enabled why not my Alteryx mail tool - 'mic drop!'.
Further explained, Alteryx is a tool that needs to live within abide by the policies and security standards in the organization not vice versa. Therefore, it shouldn't be a big surprise, or a big ask for that matter, that a mail client should have the ability to authenticate prior to sending email of SMTP. I'm very surprised this tool is so arcane. Please implement quickly. Thank you
Many workflows I work with along with those of my colleagues, use big databases in order to get some data. After a few steps down stream and testing, we normally just add an output and then open up that data in a new workflow to save time running the original workflow. Not that this is much of a burden, but I am used to copying and pasting tools from workflow A to workflow B, but you can't do that with the output, because in workflow B the output needs to be converted to an input. I just think it would be a cool added feature if possible. Anyone else agree?
Some of the workflows I use have multiple inputs that can take a long time to initially load. The new cache function itself has been amazing, but there is one big drawback for me: I can't cache multiple tools at the same time. Alteryx will allow me to eventually cache all of the tools I want cached, but it will take multiple times running the file. This still saves me time in the end, but it feels a bit cumbersome to set up.
Bring back the Cache checkbox for Input tools. It's cool that we can cache individual tools in 2018.4.
The catch is that for every cache point I have to run the entire workflow. With large workflows that can take a considerable amount of time and hinders development. Because I have to run the workflow over and over just to cache all my data.
Add the cache checkbox back for input tools to make the software more user friendly.
The SQL Editor window could have a better presentation of the SQL code; two issues observed
First, that it's simply plain text without even a fixed-width font, much less syntax highlighting
Second, if you type in some manually formatted SQL code (e.g. with line feeds and indentation), then click on the "Visual Query Builder" button, then click back to the "SQL Editor" button, all the formatting is lost as it is converted to one run-on line of code, which is very difficult to read.
I understand that going between the Visual Query Builder and the SQL Editor is bound to have some issues; nonetheless the "idea" is to allow a user friendly display in the SQL Editor window:
Use a fixed width font, (should be trivial to implement)
My "implementation ideas" are based on a couple minutes with google, so hopefully this is a very feasible request; my user base is very likely to spend more time in the SQL editor than not, so this would be a valuable UX addition. Thanks!
Right now we can create Tableau extract files (.tde), but cannot read them into Alteryx -- this limits the partnership of these two companies. Please add the functionality to import .tde files, Best, Jeremy
With the amount of users that use the publish to tableau server macros to automate workflows into Tableau, I think its about time we had a native tool that publishes to Tableau instead of the rather painful exercise of figuring out which version of the macro we are using and what version of Tableau Server we are publishing to. The current process is not efficient and frustrating when the server changes on both the Tableau and Alteryx side.
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.