You are viewing limited content. For full access, please sign in.

Question

Question

Issues with lookup-filled single line fields in Forms 10.2

asked on January 26, 2017

We recently upgraded a customer from 9.2 to 10.2.

One of the major differences in Forms is that single line fields that are filled via lookups seem to have case-sensitive filtering now, whereas previously it was case-insensitive.

This is causing LOTS of problems. Is there a way to change the filtering method back to the way it was in 9.2?

0 0

Replies

replied on January 27, 2017

I have not noticed anything as far as Case Sensitive, but I have noticed a difference with 10.2 and spacing between words.  I know there is the leading and trailing spaces, but we had an issue with some spaces between words where previous versions of Forms didn't have an issue with that, but 10.2 wouldn't perform the lookup because we had an additional space between 2 words and it appeared as if Forms 10.2 was removing that space during the lookup.

0 0
replied on January 27, 2017

I can't quite tell from your description if it's the same as the issue reported here or you meant the "where" clause in lookup is case sensitive. If it's not the same as the issue reported in the other thread, could you open a support case and attach a sample process, please?

0 0
replied on January 27, 2017

I talked to Support this morning and they said it's the same issue Pieter reported. We'll wait for the service pack mentioned.

0 0
replied on January 27, 2017 Show version history

The root cause of the issue is the same as the one from https://answers.laserfiche.com/questions/114141/How-can-I-make-autosuggest-case-insensitive-for-the-start-of-the-word .

Whether the field is using our built-in auto suggestion list, or if it's used in a lookup rule where the field is filled in with the column values, we use the same javascript to handle the front end validation of when users type into the field and it pares down the suggested values.

This has been filed as SCR 153758.

 

*Edit*

This is fixed in KB 1013831

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.