I have a Doc Lib where I have some Metadata fields.There is one field called “My Choice” which is a Choice type field with 3 values – “Choice1”, “Choice2” and “Choice3”. Now there is another field called “My Value” of Text Type.Man bekommt weder einen neu eingegebenen Wert, noch kann man dieses Feld ändern.
Sometimes the XML files don't show exactly what the database is holding.
So, if we go back to our original problem listed above.
How can we prevent a user from changing a certain column for an item in a list event?
If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.
In this article we’ll continue where we left off and see how we can add a hook in Share Point and enhance the content creation and approval process to make it more valuable to end users.In SP 2010, workflows have been made pretty obvious.