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

Question

Question

Template Fields display the token names rather than the token values - QF Scanning

asked on July 26, 2017 Show version history

Hi there,

When I run through a QF Session, a document or two will be identified and processed. When I review the document before I store it to Laserfiche, the template fields do not have the token values, but the token names listed. 

The document is a PDF and when I review the output pane, the values were pulled from the ZoneOCR and stored in the token.  

When I try to store only the document, I receive the follow errors. 

The first relating to the width of the template field, however, I do not understand the second. 

I am not using ZoneOCR tokens, I am using the "Create Assign Tokens" Tokens. 

 

0 0

Replies

replied on July 27, 2017

Hi Mason,

Have you checked the "Configure Fields" dialogue for the relevant document class(es)? Click the "Configure fields..." link in the lower right corner of the window when you have a document class selected in the Session Configuration pane:

This will open a dialogue allowing you to configure how fields are handled in real-time, as well as whether blank fields will be populated with token names instead of token values.

I'm curious--what values are you putting into your "Assign Token Value" tokens? Are you pulling data from an external source? If I understand correctly, it sounds like you might be adding an extra step to the process--are you taking the values returned by ZoneOCR and putting them into tokens you created with the "Assign Token Value" process? If so, this also might be causing you issues--you should be able to reference the ZoneOCR tokens directly in the fields you're hoping to populate.

Also, if you're getting an error re: field width, simply increase its width in the Admin Console:

I hope this helps, let me know if I can clarify anything.

~Rob

0 0
replied on July 27, 2017

I'll let you know if it resolves the issue.

0 0
replied on July 27, 2017

Yeah, I am not using the Laserfiche Capture Engine for the source. I am also using Pattern Matching Tokens instead. The pattern matching does not have either checkbox checked for the option "If the input value yields no matches".

 

 

0 0
replied on July 28, 2017

Ok, I'll play around in Quick Fields a little to see if I can determine anything else about the issue.

In the meantime, here are some possibly useful articles from on the Laserfiche Support site:

https://support.laserfiche.com/kb/1011946/a-parameter-is-incorrect-error-occurs-when-sending-documents-to-laserfiche-

https://answers.laserfiche.com/questions/69706/Editing-incorrect-information-in-Quick-Fields

What version of of Laserfiche are you using? What version of Quick Fields? Would you mind posting a screenshot of you Pattern Matching configuration?

~Rob

0 0
replied on August 3, 2017

Found out this was a bug. I was experiencing the same issue in Quick Fields scanning. 

Laserfiche created an SCR.

1 0
replied on December 21, 2017

Was this issue resolved? We are having the same issue after our upgrade to version 10. When bar codes are not recognized the the token gets populated in the metadata filed like %(Barcode PILR1)

0 0
replied on July 24, 2019

I raised a similar issue this week and was informed that for my issue at least (where in some scenarios I see the same in that the token names were appearing rather than the value, or blank) a fix is not yet available but will be included in the next release

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

Sign in to reply to this post.