Hi,
In the past I used these two blog posts:
http://blogs.msdn.com/b/sharepointdev/archive/2012/04/16/programmatically-create-a-managed-metadata-list-column-mohammed-faizan.aspx
http://www.wictorwilen.se/Post/How-to-provision-SharePoint-2010-Managed-Metadata-columns.aspx
They both use a
Thanks for the update, I’ll have to check that.
Wes
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Nigel Witherdin
Sent: Thursday, September 12, 2013 4:54 PM
To: ozMOSS
Subject: Re: Managed Metadata Fields
Yeah I do the same thing and hook the mm field up to
Yeah I do the same thing and hook the mm field up to the termset through code,
however if your field declaration includes the WebId or SiteId attributes, or
the properties shown in my first post, then the field will appear to correctly
hook up to the termset, but won't behave correctly.
Oh hell yes! Naming conventions are important EVERYWHERE. XD
On 12 September 2013 12:20, Sezai Komur sharepointse...@gmail.com wrote:
whoah 2,000 characters is way to long.
A descriptive page URL, containing words, delimited by dashes is a good
thing. You shouldn't make it excessively
