Forum Discussion
Mandatory columns on new doc library experience
Yes, it's a known behaviour and it's by design. Basically metadata is not enforced in the modern UI in SPO Document Libraries
If this is "by design" does this mean that metadata will never be enforced in the modern ui in SPO doc libraries? Or is it simply a known limitation that exists right now that will be fixed in the future? What's the rational for not implementing this in the new UI? Many of my clients make metadata required for a reason, especially for records management. For them saying it's by design and will be this way indefinitely would not make for happy clients.
- Mar 21, 2017For now, it means that metadata will never be enforced in the modern ui in SPO doc libraries
- BenSteginkMar 21, 2017Steel Contributor
While incredibble disappointing to here this (unless there is something on roadmap that is under NDA that can't be discussed here) thank you for the info. At least I can tell my clients using required columns to avoid the new UI for the foreseable future.
- DeletedMar 31, 2017
Good find!
We've just been testing this and found:
Turning on enforced check-out, will complain about missing mandatory columns at check-in time, so is a potential solution.
Lists are fine (no equivalent of upload).
This guy has done a blog post on it.
I've now put this on UserVoice.