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.
I had posted in the Tool Master | Unique thread about how when I use this tool it does not preserve my sort.
This seems odd to me. I understand that it's "a blocking tool and that records are then sorted prior to executing the tool process" as @TaraM points out. However, in a program where data is explicitly manipulated to a condition, there is an expectation on my side (maybe mistakenly?) that if I sort something that it would not be changed unless stated or indicated in some fashion.
For my use case I was sorting to eliminate the duplicates, then joining that data to eliminate other duplicates and outputting the resultant to my users and future-state will be automatically fed into a system, for each stage it matters that the sort function is kept intact.
I know it's a simple complaint / fix, but its unexpected behavior on my end and could mean less confusion and less tools on the board. which is always a good thing in my book.
Wonder if it would be possible to have a set of SQL tools in Alteryx which to the user would look like you are dragging in a tool to manipulate the data (such as filtering data) but in the background it is updating the SQL (such as adding a WHERE clause) meaning the module runs faster. This would be easier than having to manually update the SQL code and would run quicker than bringing all data through and filtering afterwards.
I know there is currently the Visual Query Builder, but this is quite fiddly to use so would be good to have something more user-friendly.
The join tool right now does only inner joins, requiring the use of the union tool to emulate outer joins.
By itself it works fine, however when having workflows involving a large number of joins and unions with lots of data in it performance is severely impacted, leaving to situations where Alteryx Designer slows down massively even with extra CPU/RAM available.
Idea: Create a UX feature to provide a cursor area magnification.
Problem: One of the challenges of working with Alteryx is quickly navigating around the canvas. Traditional software editors have bookmarks or anchors that let you quickly jump to predefined parts of the code.
Alteryx does not have these. Instead, the tools available are the Find tool, Zoom tools, and the Overview window. While capable, they still require a lot of typing and clicking, panning, zooming, etc.
Solution: Create a small magnification window that would follow the cursor around the canvas. This is commonly known as a Loupe feature in many image editing software such as Aperture.
Benefits: This would allow a user to have a full view of their entire workflow and yet be able to see and configure a specific tool with ease.
Activation: I think this feature could be activated in two ways. 1 - The user could toggle the feature by clicking a keyboard shortcut 2 - The feature would automatically enable once the zoom was out beyond a predetermined level.
Options: The user would be able to shrink or enlarge the size of the magnification window.
Example: I've mocked up an image of what this might look like below.
It would be nice to have the option to open a macro from the configuration window. I often use the find tool to locate macros and sometimes they are in collapsed tool containers or buried under other tools and it makes it difficult to right click on the tool itself. The find tool brings up the configuration window so if there was a button on that window it would make opening the macro more efficient.
One of the handy features I really like about Alteryx's standard Join tool is the way you can select and rename fields right in the join tool. It would be great if this feature could be added to the IN-DB join tool. Whenever I perform a join in DB, I ALWAYS have to add a select tool after it since you always want to de-select one of the redundant fields that the join was based on i.e. (ID and R_ID).
Behind the scenes, I'm sure the select feature would still have to be handled as if it were a separate select tool, but it would just be convenient if the user interface could combine those two features.
Many features are in the form of categorical variables. It would be amazing to have a set of tools for clustering and dimensionality reduction on categorical variables.
The current tool set in Alteryx is fantastic for working with continuous variables (k-centroids, KNN, PCA), but falls short when working with continuous variables.
There are some ways to do dimensionality reduction on categorical variables (Multiple Correspondence Analysis, PCA with gower's distance, etc.) and some ways to cluster categorical variables (k-modes, working with medoids instead of centroids--PAM, etc.).
Some key considerations on which algorithm to use are time complexity, validity of results, and whether the algorithm can work on variables that are only categorical, or both categorical and continuous.
While scrolling through the analytics gallery, if I click on a tool on page 5 to read the details and then hit back key, it takes me back to page 1. It would be nice to just go back to my previous page.
tl;dr It would be great if auto-detected assets on output tools were included when exporting/saving to the gallery.
Suppose I have an output to my C drive and try to package that file when exporting or saving. It gives me the option to package my file:
The only problem is, that file isn't actually saved with the package; instead, it just creates an externals folder where it will write the file to. But the file itself isn't included. The current work around is to go to your output tool and add that file manually as a user asset:
Notice that I had to manually add the same file that was already auto-detected. Now when I go to export, I get the same screen as before:
The big difference is that now that I've added the file as a user asset, the file itself is included in the export.
In conclusion, it would be great if auto-detected assets on output tools were included when exporting/saving to the gallery (so that it has the same behavior as user-added assets).
Currently, there is a setting in the table tool to control the decimal places of all values by column. This is not only unnecessary, but it actually screws up any data that comes in where the ROWS may have different number of decimals. The only way around it is to convert everything into strings, which is annoying. Please just get rid of that column setting! Or enable the same setting inside the row rules.
Hi - I was attempting to build a workflow as an analytics app that could notify the user with a message when there is fallout from certain joins that needs to be reviewed. Not all fallout is bad fallout, so I would not want the message to stop the workflow form running, but rather give a friendly reminder to verify that the fallout is okay or immaterial. It is my understanding that their is currently not a solution to this after speaking with the support staff.
Since the Geocoders create point data, having the spatial field recognized as a centroid can be helpful to the user. If it's marked as a centroid, it makes it easier for the user to differentiate between point vs polygon/line, especially if the user is already using polygon data in the module. If I do a Spatial Match or Join, I can have two fields called SpatialObj, which I have to track back to figure out which is which. If after combining, it showed Centroid for my geocoded points and SpatialObj for my polygon data. Kind of like you do for the Create Points tool, if I use that the field is called Centroid.
It would be great to be able to output a report to Adobe Illustrator (.ai). This would allow us to refine the presentation, or hand it off to a graphics department to do that for us. It would especially be great for the map reporting tool, as many GIS people finish maps in AI to give a more polished result. This would allow Alteryx to compete better with Esri as far as map creation.
I can only really speak to map creation, but please comment if you have another use case.
Field selection in Multi-Field Formula seems to be 'All' or 'All of a Type' or, potentially, lots of manual tagging. I have >600 fields and want to select about 150 adjacent fields. Is it possible to implement a 'mass select' option within the Multi-Field Formula Tool, as found in other tools?
so that you could easily tell Alteryx what character class you want, as outlined here:
Currently, it is very hard to look at the documentation, and know what characters encompass what class. Adding this would be extremely useful. The only way I found the syntax was through the formula menu, which is depressing that its not on the function reference page itself: