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.
Could we please change the Interactive Chart tool, to:
recognize when upstream types have changed and reconfigure (in the case of numerical types marked as string)
For line charts - sort the values in order of the X value
Sample Flow - derivation of challenge 201:
- The first interactive chart on this flow has no sorting at all performed by the charting tool - this may be due to the fact that the X & Y axes are in string fields. Generally line charts would attempt to sort both the axes and the values (where the values should order according to the X axis). Please can you add a default sort anyway?
- If you then change the data types on these fields to be numeric - the charting tool still does not sort them until you reconfigure the tool manually - REquest: please can you get the tool to remember the data types, so that it can prompt you; or even better just reconfigure?
(image looks identical after retyping the fields)
- When you do a manual reconfigure of the tool after changing the types - the axes are sorted, but the values are not - so you end up with a chart that crosses back and forth. Generally line charts are ordered in the order of the X Axis for the values
- Request: Please sort values on the line chart automatically in order of the X value?
NOTE: Finally got the outcome needed by forcing the sort before the interactive chart tool
The select tool does a great job at flagging up when something has changed from its original state. However why does this not happen with the checkboxes to keep or remove a field? It would be much faster and easier to read if we could have the same color conditional formatting as the rest.
I personally think it would work better to tab from 'Select Column' to 'Enter Expression Here' and not the 'Functions' List as probably people who are tabbing would immediately like to start typing the formula rather than going through functions, fields, etc.
When writing an expression in a Formula tool, I love that you can just type an open bracket and suggestions pop up that allow you to auto-fill the rest of the variable name. What I find frustrating, however, is that once you type the open bracket, the highlighted field automatically moves to the one where your mouse is pointing, regardless of if you have moved your mouse or not. I think it makes more sense to always highlight the first field in the list and only take mouse position into account once it has actually moved.
It is hard to describe in just a picture as opposed to a video but essentially I had my mouse below where I was typing in the screenshot below then when I typed the open bracket, the 3rd field listed automatically got selected even though I never moved my mouse.
The following idea might not be as valuable as some of @SeanAdams posts, but it would save this user precious fractions of time. When I leave the canvas with my mouse (point A) to go up to the pallet I select and drag the tool down to the canvas. Sometimes I do right-click and go through the menus to add the next tool, but generally I go through that labor only when I'm inserting in-stream the tool. So here is my idea:
Double-Click your NEXT tool and it "Alteryx-ly" appears on your canvas in proximity to the hi-lighted (last) tool. Better yet, connect it! Now I can move from the pallet to the configuration panel directly without having to move my mouse down to the canvas and then over to the configuration panel.
Hopefully, my friend @Hollingsworth will find this time-saving idea worthy of a star. Speed demons like @NicoleJohnson and @BenMoss might not need this turbo boost, but at my age it is worth the ask.
It would be helpful to differentiate between annotations that have been automatically generated, vs those that have been manually entered. This would help speed up "reading" workflows, and reduce any confusion that occurs when annotations have been manually amended - but might look like auto-annotations.
E.g. auto-annotations appear Grey, whilst manually edited annotations appearing Black?
Could you please change the order of workflow names in the 'Active Documents' button to be ordered in the same order as the workflow tabs and not alphabetically as it currently is?
When you have more than 5 workflows open (or less if they have long names) it's so tricky to quickly and easily cycle through them to find the ones you need. This is especially important when demoing, training and presenting to others!
I love the new right click and duplicate workflow feature, but I think the duplicated workflow that opens, should open next to the original workflow and not at the end of all of your already open workflow tabs...
Can we have an option to save a workflow in a prior version for backward compatibility? I think Tableau offers this functionality.
If I have 2019.4.8 and a colleague has 2019.1.x, I cannot share my workflows because my colleague will receive a notice that the workflow was built in a newer version. I want to be able to save my workflow in 2019.1.x and send to my colleague.
This is predicated on the workflow not containing any tools/features not present in the older version. In that case, give me a warning about the specific tools/features that are not backward compatible. Thank you.
I'm digging the new holistic data view in the browse; however, there is one aspect of the old view that I miss: I liked the list of top values to be available without scrolling. Here is the current view of the new browse:
What are my top values? I either need to hover over the blue bars, or scroll down to see the list at the bottom. I would like the top values list moved to the top. For reference, here is what the old view looked like:
My top values are available right there at the top.
Rephrasing his idea as mine: The tool defaults the expressions to use [RowCount]. If you should either "Update Existing Field" or change the "Create New Field" the default expressions MUST be updated manually. Please update the expressions to make use of the new field.
Well, that doesn't always work! Often it will. But if you change the TYPE to date, it certainly won't. In fact, I see many questions about joining from within a DATE RANGE and the technique to build date rows from the range requires the use of DateTimeAdd(). Wouldn't it be nice (like your sample workflows) to modify the default expression based on the change of data type? I think so.
If we were thinking easy. Suppose you could have a RANGE function (dates or numerics) where you simply selected the from, to fields and gave the user the option to select the units. Now the tool auto-configures itself to create all of the "days" between the from and to dates or "1.0" and it creates all unit values between the two numeric amounts.
These would be "Alteryx" worthy enhancements in my opinion.
We have a need to be able to trace the lineage of fields being processed through Alteryx - and it has to be done at a field level to satisfy our regulator. In essence, we have to be able to show exactly where a particular field came from, and demonstrate that we can trust this field. NOTE: If we could do this - then we could also use this information to make EVERY canvas faster, by checking for unused fields and making suggestions to remove these unused fields early in the flow.
In order to do this - it would be great if there were an option to force explicit field names in the Alteryx XML so that we can trace a specific field.
Alteryx currently only makes a note of a field name if it is changing that field which is very economical - but it makes tracing fields impossible.
Desire is for every tool to write the field list to the XML definition for every field that it knows about (just like it looks in the UI)
When you are navigating within the text input tool, it would really help if we can navigate to next/previous cell upon pressing right/left arrow keys. If the cursor is at the end of a cell value then pressing the right arrow should go to next cell. Similarly, if the cursor is at the beginning of value of a cell, it should go to previous cell.
It can be daunting to find the tool that is currently being processed by the engine in workflows that contain hundreds of tools with many ins, outs, and branches. During runtime, I want to be shown the tool that is running on the canvas. This functionality should be in the form of a button or something to direct focus to that area. It should not be the default.