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

Question

Question

Quickfields Basic Retrieval / QF Document Processing Doesn't Always Respect ordering by Path

asked on October 25, 2015 Show version history

Running a bates stamping session that is supposed to apply a permanent number in sequential order by matter then by document.

Example:

[NON-CONF MATTERS]\[MATTER FOLDER 001]\[document001]

[NON-CONF MATTERS]\[MATTER FOLDER 001]\[document002]

[NON-CONF MATTERS]\[MATTER FOLDER 002]\[document001]

[NON-CONF MATTERS]\[MATTER FOLDER 007]\[document001]

 

When using the LF Capture Engine with the Basic Retrieval (include subfolders option);  I have seen results where an item in  [MATTER FOLDER 007] gets a Page Number Stamp that should have been applied to [MATTER FOLDER 002]\[document001].  I need the documents presented for stamping first by what folder they are in, then by in Alpha order in that sub-folder.

Thanks

 

 

 

0 0

Replies

replied on October 26, 2015

If you're going through subfolders, then the order is alphabetical over the entire set of documents, not including their paths. If you have multiple documents with the same name, but different paths, their order is not guaranteed.

1 0
replied on October 26, 2015

Thanks Miruna.  That can really put a kink into bates stamping muliple folders.  I'm assume there is no workaround save changing the source to look at one sub-folder at a time.  You might consider added some kind of sort order dialog in QF capture version 10

1 0
replied on October 26, 2015

One workaround might be to initially add characters to the beginning of the document name according to the folder it's in, such that documents in the same folder are grouped together when sorted alphabetically by name. How you do this depends on how your documents are initially imported into Laserfiche. 

Then your Quick Fields session could remove these extra characters from the document name, so that your document names look normal after processing. 

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

Sign in to reply to this post.