Equal filtering Case Sensitive MDA
None
When you use a MDA table in any part of Gainsight currently the 'equals' filter in case sensitive. When we built this initially we meant to treat equals as true equals. We would like to see this not be case sensitive as this can cause potential issues when using many parts of Gainsight.
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 username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Ideally, all filters are not case sensitive. However, the inconsistency is also an issue since the user doesn't think case sensitivity is present since some of the reports work fine.
I have also faced these issues many times. So whenever I am dealing with MDA Objects I will choose Contains/Starts with operator instead of Equal to.
Screenshot: with Equal To
Screenshot: with Contains/Starts with
Thanks all for pointing this out. I will discuss more details on this with the team to see if we can solve this problem (without causing additional problems).
Also having this issue for a dashboard filter, where I can’t pre-set it to be contains or starts-with without also putting a value in (and I want to leave as blank by default)
So users are putting in = red (instead of Red) and getting no results.