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

Question

Question

List field gives an error [V0951] , but when the error is clicked, it goes away.

asked on May 14, 2018

I'm using a pattern match to extract data to be used in a list field.  When the session runs it extracts the text and inserts it into the field with no issue.  It gives the little red exclamation mark that indicates an error.  Normally when the exclamation mark is clicked it will display the error.  But in this session, when it is clicked, it goes away, and the document can then be stored.  If the cursor is hovered over the exclamation mark it will state the value X is not in the list of values.  But for X it has the whole OCR region listed instead of just the data that has been extracted.  The data in the field itself matches up with the list perfectly fine.  I closed and reopened the session a couple of times allowing the metadata updater to run.  I've got 2 different patterns that I can use to extract the data, and with either of them, it gives the same result.  Any ideas?

 

Thanks,
Frankie 

0 0

Replies

replied on May 14, 2018

Pattern Matching defaults to returning the entire input value when no match is found. This can be changed in the token's properties.

0 0
replied on May 15, 2018 Show version history

Hi Miruna,

That option is not checked in the token properties.  Normally when the value doesn't match up with any of the values in the list, the error will stay there until corrected.  The drop down list doesn't have to be opened to chose a valid value.  Simply clicking on the error flag will make it go away.  It's almost like it went back and said "oops".  Is it possible QF is not looking up the values during the session?  There are 2 other dynamic fields that are populating with no issues.  

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

Sign in to reply to this post.