Hi Team,
Posting this enhancement request on behalf of customer.
When a source data for an identifier for instance email is having case insensitive data at source and is loaded into Gainsight, that particular data wouldn’t be resolved at 360 level and will be invisible since the query looks for case insensitive data.
In order to make sure that data is resolved at 360 pages, customer would have to make sure that whatever is the case in Gainsight is matched with Source data.
For instance if I have email as Jagadeesh@gainsight.com in source and in Gainsight this email is jagadeesh@gainsight.com this data will not be correlated since the casing is different in both places.
It would be great if we can support case insensitive matching via backend querying to show them for corresponding company 360 pages.
Regards,
Jagadeesh
