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.
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.
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.
A functionality that my team really needs is the ability to use update and delete statements through in database tools. We use Teradata on my team and I'm sure many other platforms also need this functionality. I am really shocked and disappointed that in the update to 2018.4 Alteryx decided that it would add this new functionality to it's Write In DB tool, but only added it for SQL server. Moreover, this functionality is a hole that has been missing in these tools for a long time. Patches in functionality like that need to be added to all platforms, not just one. So please add update functionality to the Write In DB tool for Teradata and other platforms. The original post where Alteryx decided to make only this small change is here: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/In-Database-Update-and-or-Delete/idi-p/13153...
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?
In some of our larger workflows it's sometime tedious to run a workflow in order to see some data, when adding something in the beginning of the workflow. Running und stopping it as soon as the tools gets a green border is sometimes an option.
It would be convenient to have an option in the context menu to run a workflow only until a specific tool.
In effect, only this specific tool has an output visible for inspection and only the streams necessary for this tool have been run - everything else is ignored and I'm fine to not see data for the other tools.
This would speed up the development of small parts in a larger workflow much more convenient.
PS: Yes, I can put everything else in a container and deactivate it. But a straight forward way without turning containers on and off would be preferable in my opinion. (I think KNIME as something similar.)
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.
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.
When we create new workflows, we like to have them in our company template, to stnadardise documentation. This makes it easier for a supervisor to review, and for a colleague to pick up the workflow and understand what is going on. For instance, we have all data input on the left, and all error checks and workflow validation on the right, and a section at the top with the workflow name, project name, purpose etc. We have a workflow that we use as a template with containers, boxes and images all in the appropriate places
It would be great if there was an option to select a workflow as a template. When a new workflow is opened, it would load this template rather than having a blank canvas.
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. )
At the moment if a part of your python code takes more than 30s to run, Jupyter times out and Alteryx cancels the workflow. This makes the Python Tool unusable for anything intensive and the timeout should be removed by default or be configurable per workflow.
I've made this idea as none of the solutions in these threads feel satisfactory:
We need an option to schedule a continuous bi-weekly payroll workflow. It is every two weeks starting on a certain day of a week. Some months have 3 and other have 2. If we had an option to select the starting day in a particular month and then select bi-weekly bullet (or every 2 weeks) from that date it would be perfect. thanks
We are working on building out training content in a story mode and would like to have short snippets playing in a loop for people to see embedded in the workflow. Currently you can add a .gif to a comment background and it will provide a still image on the worklfow itself but functions as a gif in the configuration display. The interesting part is when you are running the workflow the .gif works and then it pauses it when the workflow has completed!
Example GifGif upload in comment and playing in the configuration windowGif in workflow when uploadedGif after workflow run
As a Server 2018.4 admin, I need granular control of Server/Gallery defaults including:
1.) Pre-allocate AD users and groups (under Permissions) to specific Studios
2.) Control defaults for scheduling/priority/worker settings on Users
3.) Control defaults for workflow download/no-download at Gallery or Studio level
4.) Control defaults for notifications. Currently I have to check each notification template individually to disable it. Change template tile colors (or whatever) to provide visual queue as to which are enabled or disabled.
Above all, the tiled approach to displaying users, groups, studios simply isn't scalable. A simple data grid type display will allow higher information density allowing settings like: sharing, download ability, scheduling, credential type settings (studio default, artisan specified, runtime entered etc) to be easily reviewed. Basic server governance relies on easy visibility (reporting) of settings to ensure consistency...
This one may be a slightly niche request, but it has popped up a couple of times in my work so I thought I would submit. When importing multiple sheets from an Excel workbook using either the Dynamic Input or wildcard in the Input Data tool, I sometimes get an error that the schemas don't match. While this initially seems like the headers may be different, it can often occur because Alteryx is casting the columns as different data types (as I understand it, based on a sample of the incoming data). While this is often helpful, in this case it becomes problematic.
This has been asked several times on the discussion board including here and here. To workaround this issue, I have gone the batch macro route, but this could be solved more simply for the end user by adding an additional checkbox to the Input Data configuration when an Excel file is selected that imports all fields as strings (similar to the standard CSV input). Then the schema could be specified using a Select tool by the user once all of data is brought in.
I'm not sure if this would be valuable for other input data types where a schema is more explicitly specified, but for any where Alteryx is guessing the schema, I feel like it could be helpful to give the user a bit more control.
When you left click + drag across the canvas you can select multiple tools. When you hold control and do this twice, the first selection gets deselected. The suggestion is to combine these selections into one. Much like when single selecting tools and holding down control, but for multi-selecting. Just a small QoL issue.
Selection of blue box should be added to the already selected tools