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

Question

Question

Change Request - WebDav file extension

asked on October 28, 2016

When accessing Laserfiche through WebDav (using Windows Explorer), when documents doesn't have any extension in the Laserfiche document name, then no extension is present when looking at these documents through Windows Explorer. SO the associated application can't be done and can't be opened.

Can Laserfiche change that behavior (on the server side) where if there is not file extension in the document name (compared this to the internal system extention field for this same document), then add an extention to the document name so all WebDav side documents have a file extention.

0 0

Replies

replied on October 28, 2016

Hi,

I think not having an extension with a file is some kind of security feature, where even though those files are in there raw format but are not accessible without LF SQL database.

So for someone to actually read it, have to have access to both volume server and database server. 

0 0
replied on October 28, 2016

Hi,

I am not talking here about accessing files within volumes that are stored server side.  I am talking about having access to the Laserfiche repository content using the WebDav technology. 

0 0
replied on October 28, 2016 Show version history

sorry i misread your question. i see in help file that extension has to be part of file name. I see what you mean now,

0 0
replied on November 22, 2016

Checked with Laserfiche Server team, it is not doable to show the extension in the name when the name doesn't include it when the document is created.

You should have all the users checked the option "Retain file extension in electronic document names" . You can add an attribute calls "[Options]RetainFileExtensions" to Everyone trustee and it will apply to all users that don't have this attribute set at the user level. For users that do already have this attribute set, you'd have to update the value.

 

For those document already created in the repository, you need to change the name to include the extension manually.

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

Sign in to reply to this post.