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

Question

Question

Unable to store documents in LF repository

asked on December 4, 2015 Show version history

Hi all,

Please note that while scanning a created document class, I am getting the below error message.

I want to capture the Customer No. and Invoice Date on the scanned image and store the document in LF repository.

On Page Processing, I have defined two OmniPage Zone OCR respectively to capture both Customer No. and Invoice Date as shown in below screenshots.

Zone 1 represents the Invoice Date i.e. 16/11/2015

Zone 2 represents the Customer No. i.e. 297672

NOTE: The customer's physical invoice is not properly calibrated.

When testing both processes, there is nothing relevant appearing in the Output tab.

Thanks to advise how I can resolve it.

Kind Regards,

Sheila

0 0

Replies

replied on December 4, 2015

What do those 2 fields look like on the document?

0 0
replied on December 4, 2015

Hi Miruna,

Please find part of the scanned document. These 2 fields represented by the arrow. I want to retrieve them on the document name. Thanks to advise.

Kind Regards,

Sheila

0 0
replied on December 4, 2015

I meant, what do they look like in the Properties pane in the template for the scanned document? You're saying you can't send the document to Laserfiche and the error in your screenshot says the date is invalid.

0 0
replied on December 5, 2015 Show version history

Hi Miruna,

This is how I configure the Invoice Date and Customer No. in QuickFields. 

This is the configuration of the document name.

 

Kind Regards,

Sheila

0 0
replied on December 8, 2015

I meant the scanned document, but this sort of works too. So, you're specifying the date as d-M-yyy. Does that match the Windows date format on the machine? Also, according to your screenshot, Zone 1 just reads "Page.", not a date. Even if you had it read all lines, you would need to run it through Pattern Matching to get the data (which you seem to do in your other post), so the date field should use the token from Pattern Matching, not the Zone OCR one.

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

Sign in to reply to this post.