Alteryx Designer Ideas

Share your Designer product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines
Announcement | We'll be doing maintenance between 2-3 hours, which may impact your experience. Thanks for your patience as we work on improving the community!

Case insensitive join

Hey all,

 

The join tool currently does not allow case-insensitive joins, but the find/replace tool does.    Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle.    Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type

 

Please could you consider amending the join tool to include 3 new options or capabilities:

- Case insensitive join

- Allow full Unicode character set in join

- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value

 

That would remove a load of work from every text-join that's being done on every canvas we do.

 

Thank you 

Sean

 

 

21 Comments
zoesaleh
5 - Atom

Here is a case study of why this is needed.

 

 Left join:

Course nameNumber of students 
MSc in Economics & Maths50
MSc in Economics and Maths50
MSc in Economics And Maths50

 

I then export this and group them together to create a mapping table (using Tableau which is not case sensitive and gives me this mapping table (right join):

Course nameClean course name
MSc in Economics and MathsMSc in Economics & Maths
MSc in Economics & MathsMSc in Economics & Maths

 

Inner join output using join on course name: 

Clean course nameNumber of students 
MSc in Economics & Maths100

 

So I loose the 50 students from the left table because of the capital A in 'And'. Once I've done some manual checks I realise this issue and have to add this to my mapping table. 

 

Using the find replace tool or using a formula to do mapping is not an option as I have hundreds of course names to map. If I convert everything to lower case I loose the capitalisation which I need.

 

If anyone has any suggestions to make this less painful in the absence of the insensitive join please let me know. 

 

Thanks,

Zoe