Hi all,

As usual the MSDN schema definitions have left me more confused than ever 
either due to erroneous content, or a general lack of it.

Content Type and List Schemas both seem unable to reference fields (custom) by 
ID or name and seem to require explcit re-definitions. I get that fieldref 
attributes within a Content Type definition are designed to override those 
defined for the field itself. But do they have to behave differently too!?

Amongst all these choice attributes we have Locked, ReadOnly, ReadOnlyClient 
and Sealed. According to the docs Locked is obsolete, ReadOnly hides the field 
from new and edit forms, ReadOnlyClient is undefined(!) and Sealed prevents 
editing either through the UI or the object model. Terrific!

In light of all this, can someone please, for the love of Gucci, tell me how 
the heck to provision content types and site columns that are locked for 
editing within the UI only??

Further Googling reveals that the ReadOnlyClient attribute indicates that the 
client shouldn't be able to set the value of the field, so this appear 
similarly useless.

Regards,

Paul
Online Developer, ICT
CEO Sydney

_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to