For instance, if I make a feature that pushes out this Site Column, will the GUIDs line up with the external Term Store as long as I use the export/import feature on the Managed Metadata Service?
While I ponder those things, here is the XML for what a site column that refers to the term store. As you can see, it's split across several SPFields.
SspId 0d8382cf-2d63-4421-a37a-b9386d0be5c8 GroupId TermSetId 7adeced1-b73e-47dc-b695-82bb28e2f48f AnchorId 00000000-0000-0000-0000-000000000000 UserCreated false Open false TextField {d9c15c13-8073-48ff-9a0c-1fdfe0707693} IsPathRendered false IsKeyword false TargetTemplate CreateValuesInEditForm false FilterAssemblyStrongName Microsoft.SharePoint.Taxonomy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c FilterClassName Microsoft.SharePoint.Taxonomy.TaxonomyField FilterMethodName GetFilteringHtml FilterJavascriptProperty FilteringJavascript
No comments:
Post a Comment