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

Question

Question

Can I use Quick Fields to run thru docs a second time to correct a field?

asked on June 24, 2015

I have used a very complicated QF session to process a huge batch of documents.  Now, I realize that one field has been left blank about 50% of the time.  Can I run those documents through another QF session to correct that one field? 

Here's what I've tried:  I created another QF session for just that one field with a configuration for that field that is more accurate.  But, when I store the document with the right answer, it wipes out all the other fields that had been collected just fine in the first session.

I don't want to run the original QF session again because of all the time I spent touching up the results (this is a very, very big batch).

Is there no way to tell QF to leave all the other fields alone?

Thx, Connie Prendergast, Flagstaff County

0 0

Replies

replied on June 24, 2015

In the scan settings make sure that Retrieve Fields is checked.

Is the value that is supposed to be in that field information coming from the document? Or is this information that is a static field that you could use workflow to populate.

1 0
replied on July 6, 2015 Show version history

There were too many individual corrections that were needed after the initial big processing that was done, so I don't want to just tweak the original session.

So, Derek, I'm looking at your reply and thinking I could create a session where I do not use any other fields other than the Amount field, and make sure the Retrieve fields box is checked off.  If I do that, the new session should only look at the one field I direct it to and leave all the others alone? 

It's been a week or two since I first looked at this problem; I'm going to try again using this idea.  The info is on the document, I just need it to grab the right spot more consistently.  I haven't tried using QF with WF. 

Thanks, Connie Prendergast, Flagstaff County

0 0
replied on July 6, 2015

No, this did not work.  The resultant document only has one field!  Actually, no matter what I tell it, I can't get this to change.  I've set the retrievals to collect the fields; I've told the config scan settings to write over top the original document instead of creating a new document.  I can't seem to find what I'm missing here.

0 0
replied on July 6, 2015

you can get it to use the original documents field values for all but that one field. You will want it to maintain the document itself and not try and identify more documents than you are expecting. 

 

Since you are pulling from the Laserfiche Capture Engine, you can set the retrieval limit of the number of pages to be 1 (if the identify-able field is on the first page). Also set the document not to be overwritten with pages if it already has pages, this will make it so you are not getting rid of pages when you only pull in the first page.

 

You do not need to use the retrieve and collect tokens activities when pulling in the documents, just go to the template and the field in question and use the original document token for that field. You can do this by setting in the "Retrieve Entries" menu for the scan settings that the template be pulled in, or its specific fields. Like so:

0 0
replied on July 6, 2015

Ken, after your post, I started looking around again for somewhere to get this working.  Then I found the Document Merging page and changed the setting to (see below).  This worked, after I made sure my retrieval folder and the Document Storage folder locations were the same!  So, it worked great.  Thanks!

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

Sign in to reply to this post.