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

Question

Question

Quick Fields Page Splitting (Splitting multiple 2 page documents)

asked on November 16, 2017

So I had what I thought was a very simple quick fields session that went horribly wrong.  I have documents coming in by network scanning using Import Agent.  Quick Fields then takes that scan (20 2 page documents) a 40 page document and breaks it into 2 page documents all with an incremental file name structure.  Pretty easy. Things went well for a few weeks.  When the volume started picking up I noticed some errors.  The document was pulling page 2 with page 19 and so on. So one document would consist of pages 2 and 19 as a single document. Previously all tests broke the document up as 1-2 3-4 5-6... 

My settings were NO first page identification and I limited document length to 2 pages.  That was the only thing I was doing.

0 0

Replies

replied on November 17, 2017

Hi there,

Could you post the session and sample documents that failed to split correctly?

-Ben

0 0
replied on November 27, 2017

Let me see if I can clean up some documents.  I guess what I'm looking for is a failsafe way to identify EVERY page so that 100 page documents get split into 1 page documents.

I have tried having no identification criteria, and had "path is not empty".  Neither have been 100% successful.

Some how the 1st page ID is failing and these documents are kicked out as unidentified documents.

0 0
replied on November 27, 2017

Without a barcode, 100% is unlikely. There will also be random noise from the scanner, stains, smudges. Can you buy some pre-printed barcode stickers and place them on the documents?

0 0
replied on November 27, 2017

Ben,

My point is, there are no criteria. I simply want it to split the document into consecutive pages.  I edited my original Quick Fields session so that it should now only split it into 1 page documents so every page creates a new document. I'm still getting 2,3 and 4 page documents.  It's very odd. Basically it failing the criteria for some reason.  I'm not sure why.  My next option would be to setup a token which I set to 1 then check if the value of the token is 1 for page identification.  I really didn't think it would be this difficult to trigger a new page.

I have attached a document. A typical scan will be 10-25 of these 2 page documents.  The documents have already been created and returned.  Now they are being scanned by remote locations.  We should have roughly 64-68,000 of these coming in small batches.  The first 2-3,000 processed great.  Then it started taking a page 2 from one document, and pairing it with a page 1 from random pages in the same document.

0 0
replied on November 27, 2017

Are you saying you're using similar settings to this but the pages aren't separating after the first several thousand? Will I need to copy this document 3000 times to test it?!

0 0
replied on November 27, 2017

It's not really possible for us to guess what might be going on without seeing the session. It sounds like you have multiple document classes and identification criteria. You should contact your reseller and open a case with Tech Support if you believe you're running into a bug.

0 0
replied on November 27, 2017

Ben YES! I originally had no first page identification criteria and the last page identification criteria similar to what you posted. However I had 2 page limits.  So it should have been processing every two pages as one document.  These are a front and back scan.  However it was taking page 1 in a packet and putting it with random other pages.   Then I changed it to limit to 1 page and it was not meeting the criteria, and turning out unidentified pages of random number of pages (2-9 pages).  So at the suggestion of my VAR I changed it to last page Identification and added a last page identification of "Path is not Empty" that continued to get multiple pages.  Now I have added a token, assigned it to 1 and then check to see if it's one in the page identification.  We have ONLY 1 page classification.

Original.jpg
UPdated.jpg
Path not empty.jpg
Last Page ID 1 page.jpg
2017-11-27_10-48-00.jpg
Original.jpg (33.59 KB)
UPdated.jpg (46.9 KB)
0 0
replied on November 27, 2017

There is one session not shown which had no criteria under first page identification.

The First pictured Session was updated to add the Path not Empty,

Second pictured Session was updated to add the Token which I set to 1.

0 0
replied on November 27, 2017

Ben, 

Also when testing it in the Quick Fields Editor it always came up correct, it wasnt until it was scheduled in Quick Fields Agent and it had run multiple times that the error popped up.  There are no records which have 1000's of pages at most 45-60 pages.  But there were 10-15 of these 45-60 page records to process.

 

Original issue:

So let's say we have Documents A, B, C, D each with two pages A1,A2 etc...

When one of these batches would go through at some point it started splitting the 45-60 page sets like A2 with D1 even though the original document as correctly ordered A1,A2,B1,B2,C1,C2,D1,D2.  It started after about 1000 total documents had been created correctly.

My solution was to then split the documents up into single pages and process them individually.  I was hoping to avoid this to reduce the workload on the server. 

So in my  solution to create single page documents, it started failing first page identification and creating 2-9 page unidentified documents.  The sessions you see above are my response to trying to create them now as 1 page documents. 

 

I still do not understand why the original 2 page documents were assembled in the A2,D1 manner as described above.  These documents have a name and ID number on the bottom that I process in a separate QF session.  I was finding mismatched ID's on pages 1 and 2.

0 0
replied on November 27, 2017 Show version history

Are you giving all the documents unique names in Laserfiche? Is it possible that some documents are ending up with too many pages because they're getting merged with existing documents of the same name?

 

The following screenshot shows the relevant Quick Fields option that controls this:

 

 

0 0
replied on November 28, 2017

It's the failed documents....but I'm not sure why I am getting any failures.  What would be a criteria which would be true for every document?  I even tried CustomToken =1 after setting CustomToken to 1 in the previous step.  Didn't work last night.

2017-11-28_12-27-29.jpg
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.