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

Question

Question

Correcting field data in QF when they don't capture correctly

asked on April 30, 2015

I am trying to correct field data that isn't read correctly when captured. And then I want to send the documents to the Laserfiche repository manually within Quick Fields.

 

It let's me correct the data, but it gives me an error as if it ignores my changes when I try to manually push them through.

 

See my print screen below.  Is there a setting or something that let's me override the field data without QF's changing it back to the bad data before sending?

In this example, the Month field it is supposed to be capturing should be "2015-04".

QF Field Capture Error.JPG
0 0

Replies

replied on April 30, 2015

Hi Robin,

If you're using Quick Fields 9, please make sure that you have the latest patch from KB 1013636 applied.

Regards

0 0
replied on April 30, 2015

Alexander,

 

I downloaded the patch and applied it.  It still let me make the changes, but then it gave me the same error and would not send manually. 

I then modified my pattern matching and got them to go through.  I have other sessions and when something doesn't capture I can always go and modify the data and push it through.  It is only on this Session that I have trouble.  Do you think it might be corrupt?

Thanks, Robin

0 0
replied on April 30, 2015

What sort of correction are you making to the field before trying to store it? The original field data that's captured and set in the field is

FISCAL YEAR FY-2015
FISCAL MONTH 201 E-04

Perhaps the line break is causing the issue. If you clear out the field entirely and then re-type in the data, does it then let you store that document?

If there's still an issue, can you open a support case with your reseller and provide a copy of the Quick Fields session and a briefcase containing sample documents and the template that's being used?

1 0
replied on April 30, 2015

I did clear out all of the data and re-type in "2015-04", which is all I wanted.

When I changed the pattern matching, I also changed the zone. I originally had the zone to capture both the Fiscal Year and Fiscal Month.  I have now separated them to two zones as Single Line.  Maybe that was the problem.

I will watch it and see if this works better.

Thank you for your quick response to this issue. smiley

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

Sign in to reply to this post.