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 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.
The introduction fo a rank tool would be hugely beneficial. Whilst there are currently means to rank using a combination of other tools formula/running total/multirow etc... a specific "Rank Tool" would be provide a seemless and smoother way to rank your data either for further analysis or purely to output this field.
This tool should include a sort by and group by functionaility as well as options for ranking (such as dense ranking or unique ranking) and in addition multi levels of ranking (ie. Rank by "Field A" Then By "Field B" etc...).
If we rename a field ‘X’ to ‘Y’ in the alteryx module, the renaming is not inherited by all the tools using that field in that module. The tools which are still using the old field name ‘X’ will fail until they are configured to use the new field name ‘Y’. Most of the tools I have worked will inherit the field renaming. It would be very helpful if the renaming is propagated to all the tools in the module using that field name.
To keep from being too specific, the "Idea" is that Alteryx Designer should do better at recognizing and handling Date/Times on input. Thoughts include:
1) Offer more choices in the Parse: DateTime tool, including am/pm. 2) Allow users to add new formats to the Parse: DateTime lists. 3) Include user-added formats in the Preparation: Auto Field tool's library. 4) Don't require zero-padding of days and hours in the DateTimeParse() function. (1/1/2014 1:23:45 AM looks enough like a date that DateTimeParse() should be able to figure it out, but it stumbles on day and hour.)
My particular difficulty is that I have incoming date/times with AM/PM components. I've gone ahead and created a macro to take care of that for now, but it certainly seems like that sort of thing would be handled automatically.
When looking at a complex canvas - my first instinct is to group this into sub-modules (e.g. "/load Data"; "clean data") to make this simpler to understand.
We mostly do this through the use of Containers.
However - it would be more useful if you could then take an entire container and convert this to a macro. This would be very similar to the way that Visual Studio allows you to take a block of code and convert it to a sub-procedure.
This would be a super-quick way to allow people to make canvasses more maintainable and easier to understand and test!
On the “Multi-Field Formula” tool, the default is to “copy output fields and Add….” I think the default should NOT copy. I’m using this tool to trim all of the blank spaces, and change the case in text fields. I often forget to uncheck it and end up with all these additional fields at the end.
With regard to the tool container, I think the default margin should be small. I build huge workflows, and putting each section in a tool container. I have to go in and change each one to small margins to condense the workspace. Perhaps in the user settings, under document, there could be a default margin option, just as there is a container color option.
Using Redshift ODBC connector, if I configure a Pre SQL statement inside an Input Tool, as soon as the Input tool is deselected (white space is clicked in workflow area), the Pre SQL statement executes without even executing the workflow.
e.g. putting a CREATE TABLE statement as pre SQL will create the table prior to the workflow being executed.
There should be no reason for the Pre SQL statement to execute until you are ready to execute the whole workflow. If there is, then the Pre SQL statement should be done outside of Alteryx.
Please change Alteryx to NOT execute Pre SQL until workflow is executed
It would be great if we could select default settings for containers, so that when they are added they could be automatically set to narrow margins and gray background (or whatever). (PS I'm going to add another idea regarding idea categories, because "tools" and "designer" aren't available categories, but that seems like the best place for this idea).
The field selection pane in Multi-Field Formula is very small and not resizeable. It is difficult to select anything other than all variables when only 4 1/2 fields are displayed at a time. Making this pane resizeable would be very useful.
Implement an option to toggle the automatic creation of the .bak file or allow a destination different than the yxmd file. Once we have our files under code control (git) the bak file is not necessary and effectively doubles our storage usage.
I often find myself combining data from different sources. It is external data I have no control of. One of the main problems I face is that columns are often named differently: 'this is a comment' in table1 is called 'a comment this is' in table 2 and 'comment' in table3.
The union tool is convenient for tables with few columns only: when the columns are many, moving them left and right is confusing and time-consuming.
I currently list and associate the column names in Excel, then use this as the basis to rename columns in Alteryx with a select tool, then do a union in Alteryx.
It would be extremely convenient and efficient if Alteryx had some kind of drop-down box to do this association. I have tehse steps in mind:
1) Alteryx tries to guess associations by column names (if two columns have the same name in two tables, they are associated to each other)
2) for the ones with no associations, rather than scrolling left and right as is now the case with the union tool, the suer would be able to choose from a drop-down list. This would make it evident that 'this is a comment' matches 'a comment this is', etc
If progress bar or overall process completion percentage can be displayed somewhere, adds great value for the users running complex processes (with multiple databases/ files as input and complex queries especially spatial queries).
It would be useful to have the count of rows show up under Browse icons once a module was run. While debugging, I often have a number of Browse icons scattered about. It would be nice if I didn't have to click on each to see how many records made it that far.
Whenever Alteryx recognizes a field as a Date, it should default to Date, not Date/Time. I don't think I'm in the minority, but I rarely need to see the date AND the time. 99.9% of all of my date fields do not have a time associate with them; such as: Open Date, Close Date, Remodel Date, Lease Expiration Date, Lease Start Date, Date Record Updated, Relocation Date, etc., etc., etc. So I always get results like 4/1/2013 12:00:00, which makes it difficult to query against without changing to just Date. I would venture to guess that most people don't use the time either, but I may be wrong. So, defaulting to just Date would save a lot of us that extra step for each date column.