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 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.
Sometimes formulas get pretty long. There are cases of deeply nested conditionals, concatenation of long strings, cases where multiple casts and parses are used, etc. where formulas get pretty large and unwieldy. The current system of wrapping lines and managing the size of the properties pane can be a hassle, especially if you are trying to use any sort of whitespace formatting to make the formulas more readable.
My solution is this is pretty simple, add a pop-out window for formulas. It could be a context menu option from right-clicking the formula box itself, a button on the bar at the top of each formula, or any number of other things.
A really good example of this is MS Access. You can right-click any text box that takes an expression and open it in the expression editor pop-up window. The current system is more like excel where you're stuck with whatever box size you're given.
I would like to have all my annotations show on top of the tools by default. I can change them one at a time, but I would like to be able to change the default setting to be "Show Annotations on the Top" always.
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.
Was very happy to see the Bulk Loader introduced for Snowflake during last release. This bulk loader is specifically available for Snowflake environments that are hosted on AWS, but does not provide functionality for those environments using Azure. As Snowflake continues to build momentum, I imagine this will be a common request. Is there something in the pipeline to add this functionality?
For an interim solution, we will be working toward developing some generic scripts/snowsql to mimic that bulk load, but ultimately we'd love to have this as part of the tool.
I like the new cache option in 2018.3, but I would like it to function a little bit different. Let's say you cache at a certain point and then continue to build after that. If I reach another checkpoint and want to cache, it currently re-runs the entire workflow (ie it ignores my cache upstream and just goes back to the beginning of the workflow); instead, I would rather have it utilize the upstream cache. Personally, caching is usually an iterative effort during development where I keep caching along the way. The current functionality of the cache is not conducive to this. Thanks!
We have recently upgraded to 18.3 and noticed that the Filter tool expression box has lost its colour coding of expression elements. The Formula tool (which still has the 18.2 look and feel) however still has the old colour coding.
It would be great if the colour coding could be included for all tools with expression editing boxes.
I like the new cache option in 2018.3, but I would like a user setting added that would allow me to 1) write the cache files to a local drive and 2) have them persist when I re-open Alteryx. Currently, the files are written to the user defaulted temp space and don't persist when Alteryx is closed down. Thanks!
In the new licensing system at licenses.alteryx.com, I would like to be able to filter the "Administer Machines" tab by permanent vs. trial licenses. This tab is really helpful to gauge usage of our licenses by user, but right now, any trial licenses that have been parsed during the procurement process also show up as active machines.This is a bit confusing and hard to shuffle through the unlicensed users vs. licensed, especially since the actual key information on that page is only available when hovering over "License Info".
The ability to filter by more than one license key would also help with this problem.
I didn't see it as in the Idea section, but questions and workarounds have been discussed in the community a few times (11/15, 3/18, 4/18), and suggestions seem to be just to buy the $400-600 ODBC driver from CDATA (or ZappySys), or I could use a VBA script in Excel trigger a refresh, or create my own Alteryx connector macro (great series btw, though most was beyond my understanding!)
While not opposed paying, kludging, or learning to program, they're just one more thing to build/buy, install, maintain, and break at the most inconvenient time
OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. OData helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc. OData also provides guidance for tracking changes, defining functions/actions for reusable procedures, and sending asynchronous/batch requests. OData RESTful APIs are easy to consume. The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools.
Data profiling feature in the Browse tool is a great feature, however, when your working with an extremely large data set, it can a large amount of time to fully render.
My idea is if Alteryx can make a pre-determination whether the data is so large that it'll take a substantial amount of time to profile the data. If it does, to not profile immediately, rather, display a message where the profile info would be letting the user know that it may take a while to generate with a "Generate Profile" button if the user needs to see it.
Another option would be to only profile a sample of the data and present the user an option to profile everything.
An ability to modify the angle of the grids created. Degree Angle input would be real simple to use and would allow for creating more appropriate grids without making really small grids and re-merging them for similar result. North South & East West grids are nice, however ability to change to NW by SE would be real nice.
There are a several ways to store the Avro schema in Hive:
Literal JSON string stored in the Hive table properties (Alteryx currently supports)
Reference to the schema file stored elsewhere
Pass in the schema as a run-time property in Hive
Alteryx only supports Option #1, but that runs into a 4000 Character Limitation which is the default schema limit in Hive’s internal DB. Is it possible to have Alteryx support the other two options to be able to support data sets with large schema definitions?
Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful.
Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline. I’ll share both files soon.
Here are the top 5 features for the Scheduler.
Workflow priority ranking. When two or more workflows are scheduled to run at the same time, ‘priority’ sets the order of execution. Priority is set at the time of scheduling the workflow. Values range from 1 to 100. If a priority is not set the default is 50. The ‘priority’ field can be read from Mongo db.
Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field.
Restrict which controller and workers a specific workflow can run on. Default is to run on all servers. At the time of scheduling a workflow can designated to restrict which server to execute on. This creates a field called ‘restrict’ which server it cannot execute on.
Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning. Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows.
Set sequence of successfully completed workflows.
FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.
Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db.
If a workflow fails you can set the number of attempts to run successfully. Report attempts greater than 1 in a new field called ‘attempts’ that can be read from the Mongo db.
Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx.
If a workflow runs more than X minutes the scheduler kills the workflow and reports a workflow error with a unique code called ‘execution-limit’. This code can be read in the mongo db. The defaut is 90 minutes and can be set to any number of minutes. Each workflow can have it’s own limit.
Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows.
Is anyone else annoyed that the default Output Options for the output tool usually need to be changed? What I've found in my couple of years of using this (wonderful) tool is that for Excel and Tableau outputs especially, the default is always 'Create new [sheet OR Extract File]'.
But when you use that option for your output tool, you can't use the Alteryx flow again; you get an error (Sheet already exists you moron, or Extract already exists stupid) (c'mon, you know Alteryx is judging you and the strikethroughs are there in spirit).
The 'stupid' is silent
If you ever want to run your workflow again, you've got to change it to 'Overwrite [Sheet (Drop) OR Existing Extract File (Create if does no Exist)]'.
I'm not sure about you, but I've been (passive aggressively?) hoping that with each new release of Alteryx, I would get a means to change my defaults. I would LOVE the option to have my output tools default to the overwrite, ratherthan create, option automatically. That one step is just... annoying to do over and over again.
So, I'm not going to be a passive-aggressive twit any longer. I am formally asking for what I want like an adult.
Can I please have an option in Options>User Settings>Defaults with a drop-down for Output tool preferences: Create by default, Overwrite by default, Append by default, and whatever the other options are generally categorised according to how the Output tools are done? I really only care about the overwrite one, but you're getting my gist at this point, right?
Now that Alteryx releases updates to Designer every quarter I'll likely be updating my copy of Designer frequently. Meanwhile, my IT team doesn't want to have to update Server every quarter to stay compatible. Problem there is, when I create workflows in the latest version of Designer they can't run on the older version of Server, nor on the Gallery.
Some features that would allow me to work around this:
If I could elect what version I want to use when uploading to the gallery.
If instead of having to upload workflows from within Designer (which thereby opens the workflow in whatever version I have installed on my machine) I could upload workflows from the Gallery website by navigating to a folder on my directory and selecting a given workflow. That way I could open the workflow in Notepad beforehand and alter the version number to match Server.
I'm guessing this is a niche problem that few others will encounter:
Not everyone is as big a nerd as me and will insist on updating Designer each quarter
Other companies may have IT teams that update Server each quarter
You can install an admin and non-admin version of Alteryx on your machine (I plan on doing this once IT responds to my internal service request).
You could use the admin version for the latest and greatest version of Alteryx
You could use the non-admin version to match whatever version of Server IT has installed and use that to upload (first opening the workflow in notepad to manually overwrite the version number to match server)
Please include IBM DB2 as an in-Database option. Currently, my primary use of Alteryx is for copying DB2 tables into Teradata for use on that server. Copying large tables and particularly joining several tables and copying the results to Teradata is too slow in Alteryx.