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

Question

Question

Scanning name convention

asked on May 15, 2015

Hello, 

 

I have a custom Date field and a Type Field which i would like to be used for naming a document when scanned in with LF Scanning Module. However if i use the Date token it is using the default value of mm/dd/yyyy instead of the custom one which i have as YYYY-MM-dd.

 

Any help would be apprecaited!

 

Thanks!

0 0

Answer

SELECTED ANSWER
replied on May 15, 2015 Show version history

Well your scanner would not need to do this every time.  You can set this as the default within the scanning interface by going to File>Options>Scanned Documents and changing the Document Name settings from <use client import settings> to Custom.

 

 

You can even push these settings through the LF Admin Console User Scanning Attributes:

 

1 0

Replies

replied on May 15, 2015 Show version history

I believe this link will help you understand how customizing/formatting a date field works, although your custom date is different.

 

Essentially, you'd want to format the date token when scanning as the following:

%(Date;YYYY-MM-dd)

1 0
replied on May 15, 2015

I see, thanks for the link. It just seems more of a tedious process for the scanner to do that every single time they are scanning a document to a folder. I guess workflow will have to be the best option here for renaming the entry.

0 0
replied on May 15, 2015

Thanks for the response Ramon! I'll have to look at using that option. My only concern is that our client will be using that naming convention for several of the folders in the repository but there are a number of other folders which use different templates, some without DATE fields. I just wish there was a nice way to have each folder setup with a default naming as well. This would make it all very easy. 

 

I do appreciate your help though, and perhaps for some scanners which will only be using certain folders this might actually work. 

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

Sign in to reply to this post.