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

Question

Question

Quickfields Zone OCR character preference - Custom sequence erroring out

Quick Fields How To
Updated April 30
asked on August 9, 2017

Hi,

I've been trying to set a custom character preference sequence in Quickfields 10.1.1.216 but it returns error "Invalid parameters" systematically. Looking at the online help I seem to be using it properly. Has anyone succeeded in using this feature? Any pointers will be appreciated. For example I want to ZoneOCR a field that has 4 alpha characters and 2 numeric characters. I set the custom preference to @@@@##. Thanks.

0 0

Replies

replied on August 9, 2017

Hi,

Thanks for your post. This is a bug (reference #37841). The workaround is to add a character to the beginning of your custom character preference, e.g. (!@@@@##). Then it should work as you expected. 

1 0
replied on April 29

Eight years, later, and Custom Character Preference still does not work, showing me
"The parameter is incorrect." in all and any combinations.  

 

This is true with the exact use case from the documentation:

 

"Example: Mark is reading dates from a particular zone. The dates are always in a format similar to 08/01/2009, but sometimes the number one is read as a slash and vice versa. He sets the character preference to ##!##!##### to set the preference for each character in the string for letters or numbers, depending on its position."

Things that don't work on a standard date: ##, !##, (!##), @##, (@##) and pretty much every other combination I could think of.

 

 

0 0
replied on April 29

That seems to be a typo in the documentation, it's got 5 # characters for the year.

##!##!####  does work for me in Quick Fields 11.  (!##), @##, (@##) are not expected to work because they are not conforming to the character set supported (OCR custom preference is not like regular expression, it is constrained to the 4 symbols specified in the documentation).

Unfortunately, a full fix requires some major surgery on the OCR engine. Running the value through Pattern Matching and or setting a constraint on the field to be populated are more reliable at enforcing the format and making it visible to the user for manual correction.

0 0
replied on April 30

Thanks Miruna, I noticed that typo. Using QF 11.0.2303.30125, it does not even like two leading digits:

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...