Home Sign In

Steven Van de Craen's Blog

Bloggings about SharePoint, .NET and more.

RSS Feed
  • Contact Me

Archives

  • July 2007 (19)
  • August 2007 (6)
  • September 2007 (3)
  • November 2007 (12)
  • October 2007 (4)
  • December 2007 (8)
  • January 2008 (6)
  • February 2008 (3)
  • March 2008 (2)

Categories

  • SharePoint 2003
  • SharePoint 2007
  • General
  • Office 2003
  • Office 2007
  • Excel Services
  • Dynamics NAV
  • SOAP
  • Search
  • Search Server 2008
  • .NET
  • CKS
  • IIS

Recent Posts

  • CKS:EBE 2.0 Final Release
  • TechDays 2008 wrap up
  • SharePoint Errors: 6482, 7888, 6398 and 7076
  • Feature Activation Dependency + Hidden = Automagic
  • FieldRefs node in new Content Type XML

Other Blogs

  • //BLOG: naked programmer
  • JOPX
  • Jan Tielens' Bloggings [MVP]
  • Serge van den Oever [Macaw]
  • Carlos Segura Sanz
  • -->Patrick Tisseghem's Blog [MVP SharePoint] -->
  • Remco Ploeg's Blog
  • SharePoint Blogs
  • Romeo Pruno
  • [email protected]
  • Andrew Connell [MVP MOSS]
  • Mark Harrison
  • Pedro Serrano
  • Clemens Vasters and the Indigettes
  • Kevin Boske
  • SharePoint Team Blog
  • Brian Jones: Office XML Formats
  • Mart Muller's Sharepoint Weblog
  • Joel Oleson's SharePoint Land
  • Kris' blog
  • STSADM Custom Extensions
  • Microsoft Enterprise Search Blog
  • Michaël's coding thoughts
  • Chris O'Brien's blog
  • John Holliday's SharePoint Reflections

FieldRefs node in new Content Type XML

If you declare your Site Columns and Content Types in XML to deploy them as a Site Collection feature, you must make sure to ALWAYS include the node. If you leave it out then your Content Type will not have any of the inherited fields of the parent Content Type !!!

<ContentType 
      
ID="0xAAA943C84244BF338428AA48DA19"
     Name="Proposal"
     Group="Custom Content Types">
    <
FieldRefs />
ContentType>

 
Categories: SharePoint 2007

Trackback Url

 

Comments

Monday, 25 Feb 2008 02:56 by Adrien Siffermann
Hello Steven, In fact, it does not seem to break the inheritance of parent fields, but only has an effect on the display of this ones in the column list of the content type. I've had the same error with one of my content types without seeing it because I didn't go to the content type page to check it, and therefore I could use the content type's inherited columns in my layouts. Anyway, it is proper to always include the FieldRefs element :) Adrien PS : Sorry for my poor English...

Leave a comment

Name

Url

Email

Comments

CAPTCHA Image Validation

© 2007 Steven Van de Craen — Powered by Community Kit for SharePoint: Enhanced Blog Edition.