I think it would be nice to be able to more easily reorder fields that you're joining by in the Join tool.
For example, I have already joined by CASS_Address and CASS_City. After I did this, I realized I wanted to go back and join on Name, too, and I want that to be first. How the tool is configured now, if I want Name to be first, I must redo all of the drop downs. I would like to be able to add Name to the next set of open drop downs then use some arrow buttons to be able to move them up in the order (similar to the Summarize tool).
Sometimes on the "Join Tool" Interface in the Config screen.
You can not scroll down to read last item. The scroll bar is not at the bottom nor can be scrolled further down.
I'd say that 95.437% of the Joins I do are straight Inner Joins.
So each of those times I have to remember to go down to the Select part of the Join tool and deselect all the fields I joined on the Right Side since they'll be duplicates.
I'd like a checkbox like below (defaulted to CHECKED) to deselect all the joined fields from the right hand side. In the rare cases where there's a need I could uncheck it.
Today, any Alteryx tool with "Select" functionality has an option for "Dynamic or Unknown Fields" which, when checked, allows any new fields to pass through that tool. This is a great function for most of the tools as you can allow workflow updates to pass through the tool without issue.
However, in the Join tool, there are some use cases where there is NEVER a reason to pass new fields from one side or the other into the tool, but you might still want new fields from a primary process. Examples being something like a lookup/cross-reference to do an inclusive join, where adding new fields to the lookup might inadvertently pass these downstream. Having the option to only allow unknown fields from one side through would greatly enhance this output.
I think it would be incredibly helpful for Alteryx to include a "Fuzzy Join" operator, similar to what is described in this article: http://www.decisivedata.net/blog/alteryx-fuzzy-join-workflow/
Virtually every client/project I work on, there is a nead to clean up data. Most of the time, that involved standardizing to some existing list of data. However, as we all know, data from differnet systems or being manually collected will not match perfectly in all cases. This is most often when I tend to use the Fuzzy Match tool.
However, I have to use a lot of weird steps to effectively create a "Fuzzy Join", which is something I've done using database functions in the past. I think it would be great if a new tool were created that would do the following:
This seems like a very common thing (I've created a macro for this anyway) that could be made to be simpler for everyday use.
Please create a way to swap or change the order of the inputs and outputs for tools with two or more inputs and outputs.
For example: When creating a workflow a join tool can end up moving to a location on the canvas that causes flow paths to cross. To fix the overlapping paths with a simple option of change order of input and output with a simple up and down would be much better than deleting the paths and reconnecting and redefining all of the join fields.
I have a set of data that contains functional mapping of cost centers of the organisation. Such mapping is maintained by an administrator in the system and he manages and modifies/add changes.
Administrator does not consider the case sensitivity and sometime may write the same function name in UPPER and Proper case say for example "OPERATIONS" and "Operations"
I need to use such mapping in a workflow where I need to extract unique function names from the mapping.
Since a function has more than one cost centers so there are multiple lines for a function name in the mapping.
I used Unique tool to do this. But this tool has a limitation that it considers the case sensitivity and reads the same word written in different case type as two unique values.
So in my case the i got two lines for the same function - one in UPPER case i.e. "OPERATIONS" and other with Proper case i.e. "Operations"
In order to tackle this problem, I used formula tool to convert entire text in uniform case type and then applied Unique tool.
Suggestion : I suggest enhancing the Unique tool to give user an option to configure it to consider case sensitivity while selecting unique values from the data.
We build some pretty robust maps with multiple connections and it would be great to copy the map tool and paste it with all of the connections when we want to tweak the map slightly but keep our original map. It is a regular occurrence for us to have a very detailed map grouping by trade area name and then may want to have an overview map with all of the same connections but slightly different layout. Tracking down the connections, reconnecting them and naming them accordingly takes a substantial amount of time even in the most organized of workflows. This function would be a huge time-saver. It would also be of value with joins and unions - anywhere you have multiple streams coming in.
I've come to realize that the JOIN tool is case-sensitive by design but it would be helpful if you could turn that behavior on/off (via checkbox?) within the JOIN tool. For those of us that work predominantly in database environments that are not case-sensitive, this default behavior has caused me problems many times. Having to force the case to either upper or lower upstream of the JOIN on both flows in order to ensure a successful join is an extra step that would not be necessary if you could disable case-sensitive with a checkbox.
Our company is still using 9.5 so if this is addressed in 10....I appologize.
Currently the Join Tool Options drop down has [Select-->Select All] and [Select-->Deselect All]. I think an additional [Select-->Select All Left] and [Select-->Select All Right] would be handy.
I have a process that joins 3 data sets to identify a specific group of data and apply certain ruling. From this created file, I need to extract the data (not the headings) from specific columns and insert into an already existing template. The template has formatting that needs to remain in order for it to function.
Is this possible?
When bringing data together it is often needed to assign a source to the data. Generally this happens when you union data and need to know things later about the data for context. It would save time to generate a source field that is assigned based upon the input connections of the union tool. Perhaps when unioning data you can assign a name to each input stream?
Seems there is inconsistency across tool when it comes to being case sensitive.
One simple example might be - For Join it works based on case sensitivity, but for Formula (Multi Row) - it works based on case insensitivity.
The Idea is to make the functionality case sensitive for all tools.
1) When some code is written in Alteryx, it works same way when coming to case consistency, and does not differ tool-by-tool.
2) It is common practice to make use of functions (Uppercase/Lowercase) to ignore differences coming out of case sensitivity for items like joining with some standardized values (like List of Values etc), so it should not be much of an overhead. At times the case related differences might be something which needs to be treated differently.
3) If a tool ignores case sensitivity, there might not be an easy way (if not - no way available) to make it work for case sensitivity as per business requirement, but vice versa is attainable making use of Uppercase/Lowercase case conversion functions.
Back in the days of Visual Basic 6, and Delphi 3 - the development environment for software coding started introducing the idea of Optimization hints - specifically looking at things like variables you'd declared but never used.
All of the Alteryx tips guides say "as early as possible use a Select tool to remove fields that are not used in the workflow" - it would be very useful if the Alteryx system did a reverse walk through the workflow (from outputs back to inputs) and suggested fields that were not used anywhere or components that could / should be removed because they don't go anywhere.
By adding a reverse-walk to a workflow (sort of like an A-B-Tree prune on a game-tree) - Alteryx could spot many of these kinds of issues - and by observing the workflow in action over a few iterations, it could identify the remainder.
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.
When the append tool detects no records in the source, it throws a warning. I would like to have the ability to supress this warning. In general, all tools should have similar warning/error controls.
If you have a field length of say 10 in a Select Tool, then you use a Left Join tool and change that length to say 4. This turns that field red - as it should. Then add a Select tool after the Union. It should say 4 in the second Select tool. But instead it says 10. If it was changed to 10 (and it wasn't) then the field s/b red.
I think this suggestion would be be ideal for the Join tool and it's related cousins (Join Multiple etc.) and would improve the experience of data blending for all users.
I am going to rely on Qlik Sense for this explanation as this functionality is native to that product.
When we bring in two data sources and use the join tool to blend we are required to select the field or fields upon which we want to base our join.
In Qlik Sense we can see our two data sources:
We can then drag them together and it will form suggestions based on data association density:
This helps with identifying how tables should be joined, and at the very least shows commonalities between data streams, based on the data within the tables and not any naming conventions.
It would be nice to have the functionality to generate suggestions based on association density between two data streams, and then to apply the join from a selection.