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

Question

Question

Quick Fields empty variable in template fields

asked on November 9

I'm currently using Quick Fields 11 to gather tracking numbers which are spread out over multiple document pages. I am then taking the collection of numbers and storing them in a multiple value document field configured in the document classification:

It is possible the document scanned may not contain any tracking numbers, and the variable will be empty when QF attempts to store the document. The problem happens at this point because the field will show an error due to the variable name in the field instead of any value:

(I've ran the process without the Remove Empty Items function and had the same results.)

I would expect the field to be empty when the variable is empty, instead of the variable name being used as a value and causing issues.  When this happens, it stops the storing of the documents and requires manual intervention.

Is there some way to use variables in document fields when values are present and leave the field empty when the variable is empty? I am looking for a way for the process to continue without interaction when no values are found in the scanned documents.

 

 

0 0

Replies

replied on November 15 • Show version history

Hi Dean, 

When a multi-value token comes back empty, Quick Fields will not clear the token name. Single-value fields don't have this problem.

One possible workaround you can try is instead of putting %(Tracking Number) in the field, leave the field blank and feed it through a token named Field.FedExTrackingNo:

 

  1. In the document class, clear the value of the FedExTrackingNo field so it's blank.

  2. Right after your aggregation step, add a Assign Token Value process. Name the token

     Field.FedExTrackingNo, make it multi-valued, and set its value to %(Tracking Number).

 

1 0
replied on November 17

Hello Shengyao,

Thank you for the response! 

This solution does resolve the issue I posted. However, in my implementation I am being limited to the first page values. I have the Assign Token Value placed immediately after the Token Accumulator for the Tracking Number matches, but the values in the document field are only the collected values on the first page with matches and I have verified there are more matches on the remaining pages.

I have tried some small variations of the Assign Token Value placement, like in the Post-Processing phase, but I have not had any success.

Am I doing something wrong? Or is there another way to make this approach work for matches on all document pages?

Thanks again for the help!

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

Sign in to reply to this post.