# Creating a relationship that’s not case sensitive **URL:** \ **Category:** Ask for Help\ **Created:** [August 7, 2020, 1:32am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671 "2020-08-07T01:32:14Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\ **Post date:** [August 7, 2020, 1:32am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/1 "2020-08-07T01:32:14Z")
Is it possible to create a relationship isn’t case sensitive? For example, I want ‘Parent’ in one sheet’s column to relate with ‘parent’ in another sheet’s column. I know it’s possible to create an array with multiple cases or simply keep everything in lower case but I am looking for a better solution. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [August 7, 2020, 2:06am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/2 "2020-08-07T02:06:51Z")
A relation will always look for an exact match, so best bet is have a column in both sheets to change everything to lowercase/uppercase and then make the relation based on those columns. It’s just 2 more arrayformulas though. ---
**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\ **Post date:** [August 7, 2020, 2:15am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/3 "2020-08-07T02:15:49Z")
Can also use IFTHENs in the editor to change values. Not sure if it works out faster, but might be quicker than doing it through the sheet. ---
**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\ **Post date:** [August 7, 2020, 2:38am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/4 "2020-08-07T02:38:37Z")
Thanks @ThinhDinh and @kyleheney. I am anticipating 50+ words in the array (1 word per cell). Based on that it’s kind of unlrealistic to create 3 array formulas / if then else for each. Wish glide would simply make it case insensitive. ---
**Author:** ![Coupons\_Deal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/coupons_deal/32/9734_2.png) [@Coupons\_Deal](https://community.glideapps.com/u/Coupons_Deal)\ **Post date:** [August 7, 2020, 2:52am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/5 "2020-08-07T02:52:54Z")
@S_C You can take approach of ID. Each word will have an unique ID and same ID you can use in other sheet. Then match by Id so you don’t need to worry about word match. ---
**Author:** ![Community\_Fridge](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/community_fridge/32/1905_2.png) [@Community\_Fridge](https://community.glideapps.com/u/Community_Fridge)\ **Post date:** [August 24, 2020, 12:18am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/6 "2020-08-24T00:18:19Z")
Can you elaborate on this? ---
**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\ **Post date:** [August 24, 2020, 12:19am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/7 "2020-08-24T00:19:51Z")
If parent\_column is parent, then Parent; else parent\_column. Could also just check if parent\_column is not Parent if that’s the only option. ---
**Author:** ![Community\_Fridge](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/community_fridge/32/1905_2.png) [@Community\_Fridge](https://community.glideapps.com/u/Community_Fridge)\ **Post date:** [August 24, 2020, 12:25am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/8 "2020-08-24T00:25:14Z")
my apologies, but I tried that I’m sure I’m doing something wrong how do i make it case insensitive ---
**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\ **Post date:** [August 24, 2020, 12:51am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/9 "2020-08-24T00:51:55Z")
It doesn’t make it non-case-sensitive, it just changes values from one case to another, when necessary. You’d then point your relation to this new column rather than the original. ---
**Author:** ![Ovi](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Ovi](https://community.glideapps.com/u/Ovi)\ **Post date:** [April 10, 2023, 7:02pm UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/10 "2023-04-10T19:02:34Z")
Do we have a solution for this , I’m also interested in creating a search but with other functionalities also in it based on some actions … but if the input is case sensitive … then it will be a hasle ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [April 11, 2023, 12:24am UTC](https://community.glideapps.com/t/creating-a-relationship-that-s-not-case-sensitive/13671/11 "2023-04-11T00:24:38Z")
> [@Ovi](#): > > I’m also interested in creating a search but with other functionalities also in it based on some actions Can you elaborate on this? I believe Kyle and me provided enough info to work on this. Basically you use a computed column to lowercase the text on both sides, then make a relation based on those 2 columns, but I’d be interested to hear more about your use case. This thread is almost 3 years old and we might have better ways to do it now.