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.
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!
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
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.
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?
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.
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.
When you add a tool in the canvas, the annotation is automatically set (for example the formula, or connection configuration etc). You can then customize the annotation text in the "Annotation" tool's tab. But sometimes it can be useful to revert to the "automatic" annotation, and it doesn't seem possible once you set it to something different.
Apparently there is currently no way to reset a tool's annotation text to the automatic value.
I've found a way to do it by editing the xml content of the file : as far as I know you just have to delete the <AnnotationText>[...]</AnnotationText> tag and reload the file, and the annotation gets back to the default "automatic" value, which is still present in the <DefaultAnnotationText> tag.
I think a simple button in the tool's annotation tab to reset it would be nice.
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.
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.
I really love how I can drag and drop a file directly onto the canvas from Windows Explorer and Alteryx knows to create an Input Data tool. But when I tried it with a folder today, hoping to see a Directory Input tool appear, it wouldn't do it. Could we have a similar functionality for automatically creating a Directory Input tool?
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.
The configuration window for the Browse tool already shows Min, Max, Average, St.Dev, etc for numeric fields. If it included 'Sum' as well it would be very useful for tracking a control total for a given field through a workflow.
You could create an area under the Interface Designer - Properties when editing a macro that allows users to select the order the anchor abreviations will appear on the final macro. This is useful if we want an input or output to be at the top, for example. Currently, the only way is by deleting and adding them again on the corect order. Not user friendly. Thank you!
I'm just submitting @neilgallen's idea from here. The labels in the results window are still white, which is no longer visible. You can barely see that they're indeed still there when you hover over them.