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 searching for Alteryx help on Google the search results rarely return the current version of the Help documentation from the Alteryx website. Instead, what often happens is that an old version of the Help documentation is returned.
For example, a search for 'Run Commend Tool Alteryx' returns links for the 2018.3 and 11.3 instances of the help page:
These relate to prior versions of Alteryx and a better result would be to link to the /current/ version of the page (the URL for which never changes).
The problem above can be replicated for almost any tool or variant of search terms.
Since Google is such a crucial resource for troubleshooting, there is a risk that (a) users will inadvertently access out of date documentation and (b) users will be confused by the presence of multiple search results.
By adding a 'robots.txt' file to web pages for prior versions of the tool these results can be suppressed from Google search results.
I spoke to an Alteryx Product Manager, Alex Polly and pitched an idea about having workflows bookmarked for weekly or monthly runs.
I run weekly workflows together one after the one, from different folders and I have to open file location every single time. So here's a thought, how about if we can bookmark workflows as a set/folder itself and one click and all workflows open up.
Chrome has this feature storing the links in a bookmark folder.
field mapping in generic in-db connection is based on Microsoft Sql Server. Given the specificity of MSQL Server field types, I would like to change that in order to at least be able to use another database. Without that, this feature has no sense at all.
I really like that I can scroll -- using my mouse -- between the tool groups in Alteryx. Can this UX be added to scroll through my workflows? I usually have a bunch open, and this functionality would be awesome to have there, too!
PS: Yes, I know I can do Ctrl+Tab...but mouse scrolling is more efficient.
Other applications I work in reguarly utilize right-click menus. Sometimes those menus seem annoying, but in working with Alteryx, I realize it’s actually quite smart because it eliminates unnecessary wrist movement. In the screenshot below, I have highlighted a bunch of fields. The boxes were previously unchecked and I wanted to check them to bring them into my workflow. I highlight them, and if I were in a different application, I would just right click and get access to everything that is in the options menu, but in Alteryx, I have to actually move the mouse to the options menu. This might seem super nitpicky, but as someone who is currently suffering from overuse injuries in my wrists and hands, I really appreciate minimal wrist movement.
I think I'm liking the new UI, but I think it's necessary to bring back save, undo and re-do buttons....
1. Frequent saving of workflows is crucial and not everyone uses keyboard shortcuts
2. The ability to undo (lots) of changes is a key part of iterating and rapidly building workflows in Alteryx and again not everyone uses keyboard shortcuts to do this.
Looks like there's potentially space to add this to the right of 'help' (I suspect this might be technically quiet difficult) or to the left of 'run', 'schedule' and 'active documents' as seen in the image below.
Out of interest, where has the 'documents' terminology come from?
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’m writing about a short-coming I see in the Publish to Tableau Server Tool v2.0 (PTTS). I work in a development environment where we use different Tableau servers (i.e. development, test, production) to support product development. One of the shortcomings of PTTS is that once the Tableau server information you are connecting to is entered, validated, and the tool is configured, you can no longer ‘see’ which Tableau server/site the tool is publishing to. I think this piece of information is quite important. I know I can always us the “Disconnect” button in the tool and re-enter the information so I know which server it is pointing to, but this defeats the purpose of entering that information in the tool in the first place.
Please consider an enhancement to the tool so we developers know at a glance where (server/site) the tool is publishing. Project and Data source names are helpful, but in a development cycle, all Tableau servers may have the same Project and Data source names across all environments.
I've attached examples of the tool options when being defined and once the tool is configured – notice server URL and Site are aren’t displayed in the tool once it has been configured.
Please update the Publish to Tableau Server connector tool to support Tableau's Ask Data feature. The data source must be recognized as an extract on Tableau Server in order for the Ask Data feature to work. Currently, all data source published using version 2.0 of the connector tool are recognized as a live data source. The work around is cumbersome and requires multiple copies of data sources to be created and managed.
At our Customer we are using SAP HANA as our main database. in the moment we can only use the ODBC Client to connect against SAP HANA. In this scenario it is only possible to establish a connection with Username and Password. It would be very good if every Alteryx Designer user can connect via SSO to the HANA Database. It would be perfect to have this as standard feature and not through an add-on.
Who needs a 1073741823 sized string anyways? No one, or close enough to no one. But, if you are creating some fancy new properties in the formula tool and just cranking along and then you see that your **bleep** data stream is 9G for nine rows of data you find yourself wondering what the hell is going on. And then, you walk your way way down the workflow for a while finding slots where the default 1073741823 value got set, changing them to non-insane sized strings, and the your data flow is more like 64kb and your workflow runs in 3 seconds instead of 30 seconds.
Please set the default value for formula tools to a non-insane value that won't be changed by default by 99.99999% of use cases. Thank you.
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.