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.au<mailto:paul.tur...@dws.com.au> W: www.dws.com.au<https://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 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
