Case insensitive join

[SeanAdams]

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

[r4upadhye]

Once we have a Case-Insensitive Join, can we then change its default settings?

For ex. can we still have an option to:- Join Case Sensitive Records Only ...?

[trymzet]

Hi, could you provide an update on this feature?

[jmoniz]

Is there any update on this feature?

[jpoz]

This appears to have been incorrectly marked Coming Soon in 2017. However, it's still a valid idea that could be considered in the future.

[JohanRanschaert]

Definitely the "case insensitive join" would be very helpful to reduce the # tools to use upfront. 

[Amin]

I'd love a case insensitive join so I don't need to create another new field or add more tools just so that the cases in the original dataset remain in the final output.

I imagine something like a simple checkbox option like the one being used for Sort [Use Dictionary Order].

[Joe_Lipski]

Hey @KylieF do you think this and @SeanAdams ideas could/should be combined?

[patrick_digan]

This seems like low hanging fruit that would be a nice add!

[okakosolikos]

+1 to this one