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

Question

Question

Limit characters which can be used for document names?

asked on June 28, 2023

Is there any way to limit the characters which can be used for document names repository-wide?

We're dealing with an integration with a system which can't currently handle certain special characters.  I have various workflow-based methods to substitute, etc, these special characters in document names, but was wondering if there was a way to prohibit it upstream.  (We can and do set the autoname criteria, but the end user can always specify their own name, for example.)

TIA

0 0

Answer

SELECTED ANSWER
replied on June 28, 2023

No, the Laserfiche server considers just about any printable character legal, and there's no way to override that.

0 0
replied on June 28, 2023

OK thanks.   It seems the characters which are invalid as windows filename/path characters can be troublesome.  Colons and slashes and backslashes, etc.

Worst case I'll use a workflow to fix the filenames on create if necessary.

0 0
replied on June 28, 2023

Huh.  Today I learned...  

Brian, it seems trying to rename a document using an Emoji symbol will generate a SQL error on 10.4.1.    You can successfully use an emoji in a metadata field.

0 0
replied on June 28, 2023

That's interesting. I can use an emoji in an entry name in our test 10.4.2 system. I doubt it was a fix in that point release; more likely is that it's a setting in SQL. It sounds like you wouldn't want emojis, but if you did the error logged on the server could point you in the right direction.

0 0

Replies

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

Sign in to reply to this post.