Skip to main content
Gainsight Employee ⭐️
tejkumar
Gainsight Employee ⭐️
December 17, 2020

Case sensitive evolution in JO calculated fields

Hi Team,

Currently when we use the email values in the calculated fields it is not handling the case sensitive values . Can we take this up as enhancement and implement it to handle the case sensitive values.

      5 replies

      sai_ram
      sai_ram
      Expert ⭐️⭐️
      December 18, 2020

      @tejkumar Thanks for sharing this here! I have changed this to idea and redirecting this to our product team. 

      If it is a customer request, you can tag here for a reference. 

      Translate
      nitisha_rathi
      nitisha_rathi
      Expert ⭐️⭐️
      January 8, 2021

      @tejkumar For your use-case, do you want it to be case sensitive or case insensitive?

      Translate
        sai_ram
        sai_ram
        Expert ⭐️⭐️
        January 22, 2021

        @tejkumar For your use-case, do you want it to be case sensitive or case insensitive?

        @tejkumar need your inputs here.

        Translate
        Gainsight Employee ⭐️
        tejkumarAuthor
        Gainsight Employee ⭐️
        January 22, 2021

        @nitisha_rathi @sai_ram 

        want it to be case insensitive.

        example: source from participant: abc@gmail.com

        target :Abc@gmail.com

        Which is not matching expected to match in the calculated field.

        Translate
          chethana
          Expert ⭐️
          March 25, 2021

          Hello @tejkumar 
          We will take this up as part of redesign. Thanks for bringing this up.

          Translate
            Terms & ConditionsAccessibility statement