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.
Case sensitive evolution in JO calculated fields
+1If it is a customer request, you can tag here for a reference.
+1
+4want 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.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.