NLU Case Sensitivity

[Susan Britt]

Is it accurate that NLU is case sensitive?  I have been unable to find any documentation or community questions about it.  I am hoping it's a bug based on what I'm seeing or something simple we've missed in configuration, but thought I'd ask here before opening a HI Case.  When actually in VA chat from ESC and within the NLU Model doing tests, we noticed we get different results when typing the same phrase/utterance using all lowercase versus when we use camel case.  For example:  an Utterance for one Intent will be "i need help with beqom".  If we test the probability typing in the exact same case, we get the expected 100% match.  If we test using camel case "I need help with Beqom", the expected Intent isn't even returned.  When trying to add an Utterance with the capitalized word, add a new Vocabulary base word with the capitalize word, or even try to add the capitalized synonym (i.e. Beqom) to existing lower case base word (i.e. beqom), we get error "There was an error reading from or writing to the database".  The actual error on the NLU Vocabularies table during this attempt is "Word already exists". It's like VA and the NLU Model "Test" are case sensitive, but of course, the tables are not so you cannot add duplicate (i.e. Beqom when beqom is already there).  This is not isolated the one system name Beqom, it's just one example.  I cannot imagine it is supposed to be case sensitive, but wondering if anyone else has encountered such.  See attached for more examples with screenshots.

[Yasmin]

Is NLU case sensitive in Paris? I'm noticing that on the Greeting intent, even though I have an utterance that says "Hello", when I type hello in (lowercase) it does not recognize the intent.
 

[Kamer Taj]

Hi Yasmin,

Yes,NLU is case sensitive.

[Paul Curwen]

In Paris regular and lookup types are thankfully now case insensitive see this for confirmation:

https://docs.servicenow.com/bundle/paris-performance-analytics-and-reporting/page/administer/natural...