Re: Content Types

2012-05-21 Thread Sezai Komur
Is splitting this document library up into multiple document libraries an
option?

Sezai.

On Mon, May 21, 2012 at 4:41 PM, Ajay akhanna...@gmail.com wrote:

 Hi Guys,

 I have a client using a document library with 30 content types and each
 has different template.

 He wants to make it more usable.

 We have looked at setting the content type ordering, which has given some
 order to the chaos.

 Can we do Grouping when people click new - it displays menus like Testing
 and then templates for testing, an so on...

 Cheers,
 Ajay



 ___
 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


Re: Content Types

2012-05-21 Thread Ajay
I have suggested splitting, but he does seem too keen.

We are looking at renaming CT by prefixing the division name before the CT
name

On Mon, May 21, 2012 at 8:55 PM, Sezai Komur sharepointse...@gmail.comwrote:

 Is splitting this document library up into multiple document libraries an
 option?

 Sezai.

 On Mon, May 21, 2012 at 4:41 PM, Ajay akhanna...@gmail.com wrote:

 Hi Guys,

 I have a client using a document library with 30 content types and each
 has different template.

 He wants to make it more usable.

 We have looked at setting the content type ordering, which has given some
 order to the chaos.

 Can we do Grouping when people click new - it displays menus like Testing
 and then templates for testing, an so on...

 Cheers,
 Ajay



 ___
 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


RE: Content Types and SharePoint 2010

2011-04-20 Thread Paul Noone
And still she gets awarded an MVP. :)

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Aaron Saikovski
Sent: Monday, 18 April 2011 2:09 PM
To: ozMOSS
Subject: RE: Content Types and SharePoint 2010

Have a chat to Elaine Van Bergen about this.
She has some very vocal and strong opinions on this topic and isn't afraid to 
share them ;-)



Regards,

Aaron Saikovski | Senior Consultant | Microsoft Services Australia
[cid:image001.png@01CC.0B4DCD70]
' +61 2 8817 9280 |È +61 410 480 971 | 7 +61 2 9870 2499 | Blog: 
http://blogs.msdn.com/aaronsaikovskihttp://blogs.msdn.com/aaronsaikovski/  | 
Web: 
www.microsoft.com/australia/serviceshttp://www.microsoft.com/australia/services

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Brian Farnhill
Sent: Monday, 18 April 2011 12:02 PM
To: ozMOSS
Subject: RE: Content Types and SharePoint 2010

You could just accept that doing things declaratively through CAML is just 
horrible and write some code to fix your columns up in the feature receiver :)

[cid:image002.png@01CC.0B4DCD70]

Brian Farnhill
Solutions Architect, Extelligent Design | SharePoint Server MVP
phone: 0408 289 303 | twitter: @BrianFarnhillhttp://twitter.com/BrianFarnhill 
| blog: blog.brianfarnhill.comhttp://blog.brianfarnhill.com/ | xbox: Noble 
Downfallhttp://live.xbox.com/en-AU/MyXbox/Profile?gamertag=Noble+Downfall



From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Alex Hobson
Sent: Monday, 18 April 2011 1:59 PM
To: ozMOSS
Subject: Re: Content Types and SharePoint 2010

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.commailto: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

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.commailto: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.commailto: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.commailto:a...@hobsonator.com
To: ozmoss@ozmoss.commailto: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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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.commailto:ozmoss@ozmoss.com 
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___

ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss

RE: Content Types and SharePoint 2010

2011-04-17 Thread Prashanth Thiyagalingam

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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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


Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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


Re: Content Types and SharePoint 2010

2011-04-17 Thread Sezai Komur
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.htmlNo
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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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


Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
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.comwrote:

 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.htmlNo
 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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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


RE: Content Types and SharePoint 2010

2011-04-17 Thread Brian Farnhill
You could just accept that doing things declaratively through CAML is just 
horrible and write some code to fix your columns up in the feature receiver :)

[cid:image001.png@01CBFDD1.357826D0]

Brian Farnhill
Solutions Architect, Extelligent Design | SharePoint Server MVP
phone: 0408 289 303 | twitter: @BrianFarnhillhttp://twitter.com/BrianFarnhill 
| blog: blog.brianfarnhill.comhttp://blog.brianfarnhill.com/ | xbox: Noble 
Downfallhttp://live.xbox.com/en-AU/MyXbox/Profile?gamertag=Noble+Downfall



From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Alex Hobson
Sent: Monday, 18 April 2011 1:59 PM
To: ozMOSS
Subject: Re: Content Types and SharePoint 2010

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.commailto: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

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.commailto: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.commailto: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.commailto:a...@hobsonator.com
To: ozmoss@ozmoss.commailto: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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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.commailto:ozmoss@ozmoss.com 
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___

ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___

ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___
ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

inline: image001.png___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types and SharePoint 2010

2011-04-17 Thread Aaron Saikovski
Have a chat to Elaine Van Bergen about this.
She has some very vocal and strong opinions on this topic and isn't afraid to 
share them ;-)



Regards,

Aaron Saikovski | Senior Consultant | Microsoft Services Australia
[Description: cid:image001.png@01CBCE95.82E00700]
' +61 2 8817 9280 |È +61 410 480 971 | 7 +61 2 9870 2499 | Blog: 
http://blogs.msdn.com/aaronsaikovskihttp://blogs.msdn.com/aaronsaikovski/  | 
Web: 
www.microsoft.com/australia/serviceshttp://www.microsoft.com/australia/services

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Brian Farnhill
Sent: Monday, 18 April 2011 12:02 PM
To: ozMOSS
Subject: RE: Content Types and SharePoint 2010

You could just accept that doing things declaratively through CAML is just 
horrible and write some code to fix your columns up in the feature receiver :)

[Description: Description: avatarpic-l]

Brian Farnhill
Solutions Architect, Extelligent Design | SharePoint Server MVP
phone: 0408 289 303 | twitter: @BrianFarnhillhttp://twitter.com/BrianFarnhill 
| blog: blog.brianfarnhill.comhttp://blog.brianfarnhill.com/ | xbox: Noble 
Downfallhttp://live.xbox.com/en-AU/MyXbox/Profile?gamertag=Noble+Downfall



From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Alex Hobson
Sent: Monday, 18 April 2011 1:59 PM
To: ozMOSS
Subject: Re: Content Types and SharePoint 2010

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.commailto: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

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.commailto: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.commailto: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.commailto:a...@hobsonator.com
To: ozmoss@ozmoss.commailto: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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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.commailto:ozmoss@ozmoss.com 
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___

ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___

ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman

Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
We have had not more luck attempting to fix up the duplicate fields using
the Object Model since it appears they are referencing the same site column.

The fields do appear to be linked. If you update one it does appears to
effect the other.

On Mon, Apr 18, 2011 at 2:02 PM, Brian Farnhill br...@brianfarnhill.comwrote:

 You could just accept that doing things declaratively through CAML is just
 horrible and write some code to fix your columns up in the feature receiver
 J



 *[image: Description: Description: avatarpic-l]***

 *Brian Farnhill*
 *Solutions Architect, Extelligent Design | SharePoint Server MVP*
 phone: 0408 289 303 | twitter: 
 @BrianFarnhillhttp://twitter.com/BrianFarnhill| blog:
 blog.brianfarnhill.com | xbox: Noble 
 Downfallhttp://live.xbox.com/en-AU/MyXbox/Profile?gamertag=Noble+Downfall





 *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On
 Behalf Of *Alex Hobson
 *Sent:* Monday, 18 April 2011 1:59 PM
 *To:* ozMOSS
 *Subject:* Re: Content Types and SharePoint 2010



 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



 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 (0x010100C568DB52D9D0A14D9B2FDCC9E9F2) 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


___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types

2010-02-21 Thread Paul Noone
Hi Peter,

This is pretty unusual because these content types should be sealed. 
Anyways...I think this is what you're after.

Page Layout Content Types
Article Page /_layouts/CreatePage.aspx
Redirect Page 
Welcome Page  

Publishing Content Types
Page   /_layouts/CreatePage.aspx
Page Layout /_layouts/NewPageLayout.aspx
Publishing Master  PublishingMasterTemplate.master(this should still 
exist in its original location)


Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Peter Milliner
Sent: Friday, 19 February 2010 3:44 PM
To: ozmoss@ozmoss.com
Subject: Content Types

Hello all,

We have had a mix up with content types.  The document site content type 
default template has been changed to a word template but this has been 
inherited down to pages and publishing pages.

So now when you go to create a page it brings up a word document template.

I have searched but cannot find the default template/s required for the 
following publishing content types.

   Article 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D');

Page

BRITNET

   Redirect 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF3900FD0E870BA06948879DBD5F9813CD8799');

Page

BRITNET

   Welcome 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF390064DEA0F50FC8C147B0B6EA0636C4A7D4');

Page

BRITNET

Publishing Content Types

   
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF39');

System Page

BRITNET

   Page 
Layoutjavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811');

System Page Layout

BRITNET

   Publishing Master 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1');

System Master Page

BRITNET


Can anyone point me in the right direction

Regards
Peter Milliner
Intranet (SharePoint Administrator)
Information Technology and Communications Unit
Bendigo TAFE
PO Box 170, Bendigo Victoria 3552
T: +61 3 5434 1510
M: 0423 913 999
F: +61 3 5434 1497
E: pmilli...@britafe.vic.edu.aumailto:pmilli...@britafe.vic.edu.au
W: www.britafe.vic.edu.auhttp://www.britafe.vic.edu.au
CRICOS Provider No: 03059A
This email is intended for the recipient only. It may contain confidential or 
sensitive information which should not be passed on to unauthorised persons. 
Views expressed in this email are the author's own and form no basis for any 
contractual obligation by Bendigo Regional Institute of TAFE, nor do they imply 
a formal endorsement by the Institute of those views.

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types

2010-02-18 Thread Tommy Segoro
Article Page is what you'll be interested in if you want to create publishing 
content types for WCM.

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Peter Milliner
Sent: Friday, 19 February 2010 12:44 PM
To: ozmoss@ozmoss.com
Subject: Content Types

Hello all,

We have had a mix up with content types.  The document site content type 
default template has been changed to a word template but this has been 
inherited down to pages and publishing pages.

So now when you go to create a page it brings up a word document template.

I have searched but cannot find the default template/s required for the 
following publishing content types.

   Article 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D');

Page

BRITNET

   Redirect 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF3900FD0E870BA06948879DBD5F9813CD8799');

Page

BRITNET

   Welcome 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF390064DEA0F50FC8C147B0B6EA0636C4A7D4');

Page

BRITNET

Publishing Content Types

   
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x010100C568DB52D9D0A14D9B2FDCC9E9F2007948130EC3DB064584E219954237AF39');

System Page

BRITNET

   Page 
Layoutjavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811');

System Page Layout

BRITNET

   Publishing Master 
Pagejavascript:GoToPage('\u002f_layouts/ManageContentType.aspx?ctype=0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1');

System Master Page

BRITNET


Can anyone point me in the right direction

Regards
Peter Milliner
Intranet (SharePoint Administrator)
Information Technology and Communications Unit
Bendigo TAFE
PO Box 170, Bendigo Victoria 3552
T: +61 3 5434 1510
M: 0423 913 999
F: +61 3 5434 1497
E: pmilli...@britafe.vic.edu.aumailto:pmilli...@britafe.vic.edu.au
W: www.britafe.vic.edu.auhttp://www.britafe.vic.edu.au
CRICOS Provider No: 03059A
This email is intended for the recipient only. It may contain confidential or 
sensitive information which should not be passed on to unauthorised persons. 
Views expressed in this email are the author's own and form no basis for any 
contractual obligation by Bendigo Regional Institute of TAFE, nor do they imply 
a formal endorsement by the Institute of those views.

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread MacDonald, Mike
To clarify - 

 

I created a list level content type and want to convert it to a site
level for use elsewhere.  Is that possible?

 

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On
Behalf Of MacDonald, Mike
Sent: Monday, November 02, 2009 9:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

 

I created a list with A LOT of columns - now I want to save it as a
content type so that the fields are accessible when creating new content
types at the top level on other sites.  Is that possible ?

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Wes MacDonald
Hi,

I am not sure it can be converted, but Gary Lapoint has some stsadm extensions 
like this one that might help you.

http://stsadm.blogspot.com/2008/02/export-content-types.html

Wes

Wes MacDonald
LIKE 10 INC.http://www.like10.ca/
1150 - 45 O'Connor Street
Ottawa, ON K1P 1A4

Microsoft MVP: Visual Developer - Team 
Systemhttps://mvp.support.microsoft.com/profile/Wes.MacDonald | 
Bloghttp://wesmacdonald.spaces.live.com/ | Mobile: 613.219.7841 | Office: 
613.755.4055 | MSNmailto:wesmacdon...@msn.com
Risk comes from not knowing what you're doing.  -- Warren Buffet

From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike [...@ibtteam.com]
Sent: Monday, November 02, 2009 11:56 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

To clarify –

I created a list level content type and want to convert it to a site level for 
use elsewhere.  Is that possible?

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Monday, November 02, 2009 9:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns – now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns - now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
Ø  For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE free range column.

Content Types should be just how it's done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns - now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
Agreed, agreed!

And there should be an easy way to either lock them down or reparent them in 
the event they become orphaned through misadventure!

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:52 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing


Ø  For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE free range column.

Content Types should be just how it's done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns - now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Turner
I think the main thing is the difference between ad-hoc and permanent columns.

List columns can be great for ad-hoc stuff and don't require anything other 
than rights on the specific list.  This can be useful.  Where they fail is (as 
Dan said) you want either reuse of an individual column or the ability to 
bundle them together into a content type.

There is a place for both, but it is a fine line...  the ultimate suggestion is 
Planning :-)

Regards,

Paul Turner
Senior Solutions Specialist

M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966
A: 66 Henley Beach Road, Mile End SA 5031
E: paul.tur...@dws.com.aumailto:paul.tur...@dws.com.au  W: 
www.dws.com.auhttps://webmail.dws.com.au/owa/UrlBlockedError.aspx

ADVANCED BUSINESS SOLUTIONS LTD
This email and any files transmitted with it are confidential and are only for 
the use of the person to whom they are addressed. If you are not the intended 
recipient you have received this email in error and are requested to delete it 
immediately. Any opinion expressed in this e-mail may not necessarily be that 
of DWS Pty Ltd.
Please consider the environment before printing this email.

From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of Daniel 
W. Brown [dan...@danielbrown.id.au]
Sent: Tuesday, 3 November 2009 8:21 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing


  For future reference, the predicament you currently find yourself in is 
 precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE “free range” column.

Content Types should be just how it’s done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you’re not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it’s fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns – now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
LOL Paul :P

You're a man full of ideas.

It may be possible to create a page, which allows you to reparent a content 
type. It would just need a custom page and some code :)
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:28 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Agreed, agreed!

And there should be an easy way to either lock them down or reparent them in 
the event they become orphaned through misadventure!

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:52 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing


Ø  For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE free range column.

Content Types should be just how it's done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns - now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
And you would be just the man to write it, yes? ;)

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:56 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

LOL Paul :P

You're a man full of ideas.

It may be possible to create a page, which allows you to reparent a content 
type. It would just need a custom page and some code :)

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:28 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Agreed, agreed!

And there should be an easy way to either lock them down or reparent them in 
the event they become orphaned through misadventure!

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:52 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing


Ø  For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE free range column.

Content Types should be just how it's done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.

Regards,

Paul
Online Developer, ICT
CEO Sydney

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
MacDonald, Mike
Sent: Tuesday, 3 November 2009 2:46 AM
To: ozMOSS
Subject: Content Types - Exporting and importing

I created a list with A LOT of columns - now I want to save it as a content 
type so that the fields are accessible when creating new content types at the 
top level on other sites.  Is that possible ?
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
Haha, normally I'd jump on it, but I'm a bit under the hammer at the moment :(

I'll make you a deal.. come down and present at the user group and I'll write 
it :P

However on a more serious note. I will add it on to my todo list and publish 
it up codeplex 1 day.

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:32 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

And you would be just the man to write it, yes? ;)

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:56 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

LOL Paul :P

You're a man full of ideas.

It may be possible to create a page, which allows you to reparent a content 
type. It would just need a custom page and some code :)

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:28 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Agreed, agreed!

And there should be an easy way to either lock them down or reparent them in 
the event they become orphaned through misadventure!

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Daniel W. Brown
Sent: Tuesday, 3 November 2009 8:52 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing


Ø  For future reference, the predicament you currently find yourself in is 
precisely why Site Columns should always be used for these purposes.
Their early should either be functionality to create a content type from a list 
.. or my preference get rid of the ability to even HAVE free range column.

Content Types should be just how it's done :P

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Tuesday, 3 November 2009 8:22 AM
To: ozMOSS
Subject: RE: Content Types - Exporting and importing

Mike, if you're not that keen on coding you can grab 
SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema 
definitions for re-use in a Site Column 
featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.
 Writing a site column feature is a good first step to developing in MOSS as 
it's fairly straightforward.

If SPSource seems a little too geeky then you can do the same thing with 
SharePoint Managerhttp://www.codeplex.com/spm. Just drill down to the fields 
in the list, switch to schema view and copy out the XML to an elements manifest.

For future reference, the predicament you currently find yourself in is 
precisely why Site