Yeah saw that element. In my Common CT i have added the RemoveFieldRef element to remove the Title field but to no effect. The Title field will remain. If i add the FieldRef for Title after the RemoveFieldRef i again have duplicate columns.
On Mon, Apr 18, 2011 at 1:24 PM, Sezai Komur <sharepointse...@gmail.com>wrote: > <RemoveFieldRef /> ? > http://msdn.microsoft.com/en-us/library/aa543602.aspx > > http://sharepointlive.blogspot.com/2009/05/content-types-inheritance-how-to-remove.html > http://www.u2u.info/Blogs/karine/Lists/Posts/Post.aspx?ID=6 > > > <http://sharepointlive.blogspot.com/2009/05/content-types-inheritance-how-to-remove.html>No > idea if this will actually work though, worth a shot. > > Sezai. > > On Mon, Apr 18, 2011 at 10:50 AM, Alex Hobson <a...@hobsonator.com> wrote: > >> In MOSS 2007 the SystemPage CT did not have the attribute Inherits="TRUE" >> so when our Common CT inherited from SystemPage and we changed the >> DisplayName we did not have an issue. >> >> If you have a look the Document (0x0101) and Item (0x01) CTs you will see >> what i mean. >> >> The Item CT has the Title FieldRef and has Required="TRUE" the Document CT >> references the Title FieldRef and has Required="FALSE". >> >> So in the Document CT Title is not required. Where in the Item CT Title is >> required. >> >> Once you get up to the SystemPage CT we see the Inherits="TRUE" attribute. >> This appears to change the game, if i try and add the Title FieldRef into my >> Common CT and updated the DisplayName i get an duplicate field instead of >> overriding the field like i use to have. >> >> BTW this is not unique to Title, it is just an example. >> >> On Mon, Apr 18, 2011 at 11:37 AM, Prashanth Thiyagalingam < >> prashanth...@hotmail.com> wrote: >> >>> SystemPage CT has already got the build-in Title field inherited >>> from 'Item' CT, and this is what is causing the duplicate error. >>> >>> ------------------------------ >>> Date: Mon, 18 Apr 2011 10:29:26 +1000 >>> Subject: Content Types and SharePoint 2010 >>> From: a...@hobsonator.com >>> To: ozmoss@ozmoss.com >>> >>> >>> >>> We have run into an interesting issue when migrating our WSP packages >>> from MOSS 2007 to SharePoint 2010. The issue is in relation to Publishing >>> Content Types. >>> >>> In the past we have had a Common Publishing Content Type called >>> CommonPublishingContentTypes which inherits from the built-in SystemPage >>> Content Type (0x010100C568DB52D9D0A14D9B2FDCC96666E9F2) found in the >>> PublishingResources Feature. >>> >>> SharePoint 2010 appears to have introduced a attribute called Inherits >>> and on the built-in SystemPage Content Type this is set to TRUE. "If >>> Inherits is TRUE, the child content type inherits all fields that are in the >>> parent, including fields that users have added." ( >>> http://msdn.microsoft.com/en-us/library/aa544268.aspx). >>> >>> In MOSS 2007 we where able to add a built-in field <FieldRef >>> ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" DisplayName="Title" >>> Required="TRUE"/> into our CommonPublishingContentTypes and updated the >>> DisplayName or Required attributes. >>> >>> If we attempt to do this in SharePoint 2010 we get duplicate fields in >>> our CommonPublishingContentTypes Content Type for Title. >>> >>> Ideas? >>> >>> _______________________________________________ ozmoss mailing list >>> ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss >>> >>> _______________________________________________ >>> >>> ozmoss mailing list >>> ozmoss@ozmoss.com >>> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss >>> >>> >> >> _______________________________________________ >> >> ozmoss mailing list >> ozmoss@ozmoss.com >> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss >> >> > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > >
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
