Idea: Prompt the user to find a missing macro instead of the current UX of a question mark icon.
Issue: When a macro referenced in a workflow is missing, then there is no way to a) know what the name of the macro was (assuming you were lazy like me and didn't document with a comment) and b) find the macro so you can get back to business.
When this happens to me know, I have to go to the XML view and search for macros and then cycle through them until I find the one that's missing. Then I have to either copy the macro back into that location or manually edit the workflow XML. Not cool man.
Solution: When a macro is missing, the image below at the right should be shown. In the properties window, a file browse tool should allow the user to find the macro.
How about a quick method of disabling a container.
Current state - Click on the container, pan the mouse all the way over to the tiny checkbox target in the configuration pane and click disable.
Future state - little icon by the rollup icon that can be clicked to disable/enable, differentiated by perhaps a color change of the minimized pane perhaps?
I know what you're thinking, "talk about lazy, he's whining about moving the mouse (which his hand was already on) 2 cm along his desktop and clicking"... but still what an easy usability win and one less click to do a task I find myself repeating frequently.
Have the option of creating and editing global constants within a workflow.
Rather than bringing in a text/numeric input and having this appended and connected to various parts of the workflow, a constant could be created and used in each instance for a cleaner, condensed workflow and robust usage of consistent data
I would love to see Alteryx add an indicator whenever a number being displayed is being truncated. For example, this picture is currently confusing:
The displayed numbers should all be equal according to their displayed value, but in reality a different number is being stored in the background. I would propose something like this:
1) Any number that is being truncated when displayed would have that red triangle in the upper right corner. This already happens when a formula tool result is truncated, but I would like for it to be displayed on all data.
2) Clicking on the cell would show the actual value, not the truncated value. This would be great when debugging.
I understand that numbers are more complex than meets the eye, and I think that changes like this would help alleviate some of the mystery (like why 2 of my numbers above aren't equal).
Super simple request: Add Exasol to the list of databases that Alteryx can run in-database queries against.
We are using Exasol to store and query large volumes of data (1bn+ rows). This works great from Tableau because not very much data has to leave the database. But when we want to process that data in Alteryx we either have to pre-aggregate the data in Exasol, strip out loads of columns or sit back for hours while Alteryx sucks down the data. The first solution requires somebody to write SQL code in the database, but we are trying to avoid that (that's why we like Alteryx). The second and third are not always viable options.
Given that Exasol is partnered with Tableau, and Alteryx is partnered with Tableau, it feels like there will be lots of Alteryx customers looking for this functionality.
In order to speed up our workflows (which are very heavily tied to databases and DB queries) it would be valuable to be able to inspect the actual queries which were run against the SQL server so that we can index to optimize these queries directly in SQL Enterprise Manager (or the same on any DB platform - we have the same problem on DB2)
The idea would be to have a simple screen where I can run the workflow with a SQL profiling turned on, and then capture the output of either the entire workflow (grouped by connection so that I can tune one database with only the queries that apply) or a specific component on the canvas.
I appreciate that this is not something that would be required by a fair population of your users - but I'm sure that this will be helpful for any enterprise / corporate customers.
all too often, we build an alteryx flow just to realise that step 8 out of 10 was wrong -so back to the beginning and rerun the entire thing. this often is tedious if your work requires a big data set.
So there is a workaround, using the Cache Macro which can be downloaded (but this does require quite a bit of fiddling with containers; disabling items; setting flags; etc) - but it would be good to allow the user to "restart from here" like you can with a powerpoint slide deck. I appreciate that this may be tricky since Alteryx may be flushing data out of memory as it goes along, so it cannot restart from any arbitrary point - but if we put the workflow into a "testing cached mode" to cache data at each step; or allowed users to set particular controls as a breakpoint and cache at these points, that would help immensely.
14 is a bit large to have as the default text size in the Report Text Tool. Can we make it a "normal" size like 11 or 12? I am always forgetting to change it when setting up automated emails, and have to go back and edit it.
Can either be a setting, or we should just change the default to a normal size.
Text in this post set to 14(4 looked close) for effect.
The ability to limit the number of records (either on a specific input tool, or via the Workflow Properties) is super useful when developing a workflow...
...but how many times do you forget that a record limit was set and then spend ridiculous amounts of time trying to figure out why something isn't working properly? (I can't be the only person this has happened to...).
Wouldn't it be fantastic if a warning/message was shown in the workflow results (e.g. "Input Tool (n) has a record limit set" or "Record Limits are set on the Workflow Properties")?
Would it be possible to specify whether a worker handles scheduled jobs, ad-hoc jobs or both? Right now it seems that the workers treat both types of jobs the same, meaning that a slew of ad-hoc jobs initiated from the Gallery could slow down jobs that are scheduled to run on a regular cadence. It'd be great if those scheduled jobs could have a dedicated worker (or workers) and have any ad-hoc jobs handled by a separate worker (or workers) so that the scheduled jobs (which might be more important) are not held up by one-off jobs.
I use macros all the time, and I would love if the metadata could persist between runs no matter what tools exist in the macro. I've attached a simple example which should demonstrate the issue. After running the module once, the select tool (4) is populated with the expected data; however, as soon as anything changes (like a tool is dropped onto the canvas), the select tool (4) is no longer receiving the metadata to properly be populated. I've added the crosstab tool from the macro onto my workflow to demonstrate that it's only a problem when the tool is inside a macro. It makes it difficult at times to work with workflows that utilize macros due to the metadata constantly disappearing anytime a change is made. The solution would be for the metadata from the last run to persist until the next run. This is how the crosstab tool is working on my workflow, but putting it inside the macro changes its behavior.
Can we make the ability for a developer using Alteryx Designer and having a workflow using in-DB tools to pass along their credentials with the workflow when scheduling to run on Alteryx Server. An individual user may have access to only certain tables in Teradata for example and the ODBC connection on Server may not have access to the same tables so we need to be able to pass along the encrypted credentials. THanks!
One of the tools that I use the most is the SELECT tool because I normally get large data sets with fields that I won't be using for a specific analysis or with fields that need re-naming. In the same way, sometimes Alteryx will mark a field in a different type than the one I need (e.g. date field as string). That's when the SELECT comes in handy.
However, often times when dealing with multiple sources and having many SELECT tools on your canvas can make the workflow look a little "crowded". Not to mention adding extra tools that will need later explanation when presenting/sharing your canvas with others. That is why my suggestion is to give the CONNECTION tool "more power" by offering some of the functionality found in the SELECT tool.
For instance, if one of the most used features of the SELECT tool is to choose the fields that will move through the workflow, then may be we can make that feature available in the CONNECTION tool. Similarly, if one of the most used features (by Alteryx users) is to re-name fields or change the field type, then may be we can make that available in the CONNECTION tool as well.
At the end, developers can benefit from speeding up workflow development processes and end-users will benefit by having cleaner workflows presented to them, which always help to get the message across.
What do you guys think? Any of you feel the same? Leave your comments below.
Currently - in order to run a series of Alteryx processes which have start-finish dependancies, you have to hack this by putting each sub-process into batch macros with fake inbound and outbound controls and a fake control parameter. Additionally, alteryx forgets the mapping of parameters if you move stuff around, and you have to re-link it all up again, running each step 1 by 1 until the next one fails.
some may say "just use Block until done"
- this only partially solves the issue if your dependency chain is one deep (e.g. create the table; and then send a summary of errors found in the table)
- this doesn't create any ability to encapsulate flows to create simplicity - so it drives the user towards having increasingly bigger and more complex canvases
If we could create a new macro-type or container-type which just allows start-to-finish dependency chaining like a sub-procedure, and which just passes on what was in the input stream directly to the output stream - this would materially improve the ability to simplify flows; and at the same time it's a cheap and easy way to allow for detailed dependency and flow control.
Happy to talk through this live with the team if that makes sense?
I love the dynamic rename tool because quite often my headers are in the first row of data in a text file (or sometimes, Excel!).
However, whenever I open a workflow, I have to run the workflow first in order to make the rest of the workflow aware of the field names that I've mapped in the dynamic rename tool, and to clear out missing fields from downstream tools. When a workflow takes a while to run, this is a cumbersome step.
Alteryx Designer should be aware of the field names downstream from the dynamic rename tool, and make them available in the workflow for use downstream as soon as they are added (or when the workflow is initially opened without having been run first).
I would like to see Global Variable being made available in Alteryx. I have seen the Global Constant being made available under Workflow "User" configuration. But this is constant and needs to be defined at Design time.
How about a Process Id that needs to be auto genearted and the same needs to be available across the formula tools used with in the workflow.
So have been using the fuzzy match function quite a bit of recently. Love the tool, however it could benefit form being able to wire in a list of 'Don't generate' keywords.
At the moment we can enter them manually, however where for example i might want to exclude city or area names etc... from the do not generate list this becomes quite a tedious manual entry task, so being able to load in keyword data from pre-existing lists etc.. would be a time saver.