File Name Length

I know what you're talking about.

I've mostly encountered errors with file name max length issues when there's a discrepancy between what Windows allows, and what M-Files allows.

TBH - I'm fuzzy on the exact details, but users will run into this, if they've drilled in several layers into many sub-views, and then one top of it, they want to open a file within a multi-file, both of which have very long file names.

You'll also note when migrating, if the file name is beyond 256 - M-Files will alert and truncate the file name. Somewhat annoying at times.... however, I think it also speaks to the larger principle that users should keep their names structured and accompany with logical properties.

If the document is related to a Committee for example - tag the Committee Object and avoid the legacy of typing the committee name into every. single. document. name.

I know what you're talking about.

I've mostly encountered errors with file name max length issues when there's a discrepancy between what Windows allows, and what M-Files allows.

TBH - I'm fuzzy on the exact details, but users will run into this, if they've drilled in several layers into many sub-views, and then one top of it, they want to open a file within a multi-file, both of which have very long file names.

You'll also note when migrating, if the file name is beyond 256 - M-Files will alert and truncate the file name. Somewhat annoying at times.... however, I think it also speaks to the larger principle that users should keep their names structured and accompany with logical properties.

If the document is related to a Committee for example - tag the Committee Object and avoid the legacy of typing the committee name into every. single. document. name.