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

Question

Question

Quick Fields not naming document from token value

asked on November 22, 2017

A majority of documents are stored immediately as normal but there are outliers that do not store, producing the error "The document name was not specified. [0829-QF0]".  The session uses fields such as ID, First Name & Last Name to name the document.  I'm puzzled as to what may be causing this because the documents that are not being stored all have values but the name is instead coming across as " %(Fields.Document) %(Fields.Colleague ID) %(Fields.Last Name), %(Fields.First Name)".

 

I saw another post related to this but it seems to be slightly different and no response was ever given as to what was causing it.  There was mention of a bug though.

0 0

Replies

replied on November 22, 2017

The name will always show like that until it is stored in the repository since the token aren't replaced until it is stored.

When they are stick in quick fields are they under a folder structure or under unidentified documents?  It may not be the name stopping them but something else.  Could they be unidentified documents?

Are there other metadata fields on the template being filled in by quick fields?  Maybe another field is bad preventing storing.  I know we have one process and documents get stuck because it can't OCR the date correctly and it doesn't fit the date field format, so they won't store until it is fixed.

documentrevision.jpg
0 0
replied on November 27, 2017

Hi Jennifer,

The documents in question are ones that have been identified, all fields have been filled in and are in the correct format.  That's what's puzzling me about this. I may just contact our vendor but I wanted to see if anyone had seen this behavior before I did so.

 

Thanks.

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

Sign in to reply to this post.