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 SPSource<http://spsource.codeplex.com/> to suck down the columns as XML schema definitions for re-use in a Site Column feature<http://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 Manager<http://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
