Home » Sharepoint 2010

Custom Managed metadata column - Not getting indexed


I've created a custom managed metadata column as per the article http://www.wictorwilen.se/Post/How-to-provision-SharePoint-2010-Managed-Metadata-columns.aspx

I'm able to see the column mapped correctly to the termset and so on. I can enter the mapped terms in this column. However when I crawl the content, I can see the cawled property getting created, but it shows "there are zero documents in the index using this property".

If I manually create a managed data column, then the indexing works properly.

This is the schema of my custom managed metadata column

<Field ID="{9CE69841-358B-486E-B39E-A130FAE3B854}"
    DisplayName=My Hierarchy"
    Group="My Custom Columns"

Any help appreciated



3 Answers Found


Answer 1

You must have a document item that uses that column for crawl to pick it up. Do that and try again.

If you ever doubt your custom column schema, deploy your column side-by-side with the one you created in the interface, then open the two columns with SharePoint Manager 2010 and compare the schema in the lists. You will find any differences easily.


SharePoint 2010 MCM. Feel free to contact me http://www.sharepoint.bg/radi


Answer 2

Thanks. Let me compare with SharePoint Manager 2010.

I didn't understand your other part of the answer abt having a document item. I added the column to a content type which inherits from Page content type and created a new page using that.

I have also tried adding the column to a content type which inherits from Document content type, but same issue.


Answer 3



“You must have a document item that uses that column for crawl to pick it up.” Radi.A metioned is mening that you have to create a new document in that library you have used this custom managed metadata column.

And for content type is same, you have to add it into a library and create a new item based on this content type and crawl again.


Seven Ma




Can someone tell me how to specify a Managed Metadata column in the schema.xml of a custom list definition in SharePoint 2010.

I created a column and when I reverse engineer it I see the following

   <Field Type="TaxonomyFieldType" DisplayName="EventCategory" List="{75883c87-b5f3-4162-9887-01176cb490b7}" WebId="2f8f5674-c89d-4b93-953a-f9754d94e5b5" ShowField="Term$Resources:core,Language;" Required="FALSE" EnforceUniqueValues="FALSE" ID="{5bd91ac3-099d-4bfe-8a05-e0078c3e6182}" SourceID="{a6acad52-5744-48ba-a91a-fc4804e60f0b}" StaticName="EventCategory" Name="EventCategory" ColName="int7" RowOrdinal="0" Version="1">
       <Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">edc08221-d108-49fa-8a97-9dc9838d27a4</Value>
       <Value xmlns:q2="http://www.w3.org/2001/XMLSchema" p4:type="q2:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">0893d850-bfb4-4cdb-a30d-20616ba9094b</Value>
       <Value xmlns:q3="http://www.w3.org/2001/XMLSchema" p4:type="q3:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">00000000-0000-0000-0000-000000000000</Value>
       <Value xmlns:q4="http://www.w3.org/2001/XMLSchema" p4:type="q4:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
       <Value xmlns:q5="http://www.w3.org/2001/XMLSchema" p4:type="q5:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
       <Value xmlns:q6="http://www.w3.org/2001/XMLSchema" p4:type="q6:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">{cec2926c-cb4a-4515-b3bd-6bb2d1e24572}</Value>
       <Value xmlns:q7="http://www.w3.org/2001/XMLSchema" p4:type="q7:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
       <Value xmlns:q8="http://www.w3.org/2001/XMLSchema" p4:type="q8:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
       <Value xmlns:q9="http://www.w3.org/2001/XMLSchema" p4:type="q9:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
       <Value xmlns:q10="http://www.w3.org/2001/XMLSchema" p4:type="q10:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">Microsoft.SharePoint.Taxonomy, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Value>
       <Value xmlns:q11="http://www.w3.org/2001/XMLSchema" p4:type="q11:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">Microsoft.SharePoint.Taxonomy.TaxonomyField</Value>
       <Value xmlns:q12="http://www.w3.org/2001/XMLSchema" p4:type="q12:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">GetFilteringHtml</Value>
       <Value xmlns:q13="http://www.w3.org/2001/XMLSchema" p4:type="q13:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">FilteringJavascript</Value>

As you can see there are a bunch of guids and attributes given.  Not sure which one(s) I should specify, and even if I do I cannot specify it in terms of guid when deploying to another server.




I've set up a Managed Metadata Service and want to associate the taxonomy with my custom content type (type list).

However when I click on add new site column and choose "managed metadata" as the value I want to associate with that column, I cannot see my managed metadata service in the term set settings table below.

Instead I get the message "this feature is not enabled for this column type".

Here's what I've checked in my settings:

- added my site to content hub while setting up managed metadata service

- checked all the boxes under Manage Properties for the metadata service and service connection (to make sure the options for consumption were set).

- ran a shell cmdlet using stsadm -o activatefeature -url http://xxx -id 73EF...

[Got the message feature already activated with the above]


Any thoughts on what I missed in the setup?





I need to add the Manged data column to a Custom List of a custom Site definition

How to do it? one approach is using feature and through object model

can this be done with elements.xml file?



I have to create a site column and an content type which uses the site column. The site column has to be a managed metadata column (TaxonomyFieldTypeMulti).

To do this i first created a site with the site column and the content type in sharepoint, exported it as .wsp file and imported to Visual Studio. This gave me a an elements.xml with some fields that were already defined in sharepoint (TaxCatchAll: {f3b0adf9-c1a2-4b02-920d-943fba4b3611}, TaxCatchAllLabel: {8f6b6dd8-9357-4019-8172-966fcd502ed2}, TaxKeywordTaxHTField: {1390a86a-23da-45f0-8efe-ef36edadfb39}) and the metadata field i created (type: TaxonomyFieldTypeMulti).

The elements.xml of the content type references all four. But when i try to deploy (using vs) it, i get my content type with all fields, except for the taxonomy field.

I couldn't find a good reference for creating site columns and content types with managed metadata on the web and so i hope one of you can give advice.

Bye, Michael



Hi Everyone. I'm helping a client set up their initial site structure in SharePoint 2010 and would like some advice/guidance regarding a scenario I've run into.

Here's the scenario: The client is a software company and has several product lines, and each product has multiple versions. One item they've requested is a document library called "Releases" where they can upload ZIP files of their product releases for customers to download. Two of the attributes they want attached to each release are "Product Line" and "Product Version." There's a "cascade" relationship between Product Line and Product Version in the sense that if "Product A" is chosen, the user should only receive Version choices that are valid for Product A.

My proposed approach: One thought I had for setting this up would be to use the new Term Store Management tool to create Product Lines with Versions underneath each Product Line. The hierarchy would look like this:

Product Lines
  > Product A
    > 1.0
    > 2.0
  > Product B
  > Etc.

I would make the Products level non-taggable but leave the Versions level taggable, forcing the user to make a selection at the version level when adding an item to the Releases library. That way I'm capturing the Product and Version all in one column, and there's no need to create cascading choice fields, lookup columns, etc.

Does this approach seem reasonable to you guys, or would you recommend a different way of doing this? From what I've read online the new term store features in 2010 seem perfect for a scenario like this (since changes to product names, etc. will be managed by the term store), but I want to make sure I'm not missing something obvious here.


Hello I have a problem with managed metadata on two different servers and would like to ask you to try it.

I assume you have managed metadata service running.

1, Open some document library in some site
2, Create column - managed metadata type and select some termset and set it as required.

3, Upload a document and fill in metadata when you will be asked.

4, Then edit properties and check, that metadata are there.

5, Save this library as template.

6, Deploy document library from this template and try steps 3+4.

My problem is, you can select metadata, but they are not saved. e.g. when you check document properties managed metadata are not there.

Can you confirm this behavior ?
Thank you very much.


P.S.: one more weird thing. If you do metadata filling using office 2010 compatible application. Metadata remain there, but they are not visible in document library properties.


I am trying to search on a managed metadata column in a list.  I have the managed metadata as a mapped property (these are automatically set up actually).

I have a column frequency (daily, weekly, monthly, yearly)

I can enter a search box

owstaxIdFrequency=#a132a333-39f1-4737-9ad4-a932482e025f   //this is the taxonomy guid for Daily.  This shows results.

How do I search on the word "Daily" in the frequency column?  (I just want to figure it out on a simple search first meaning just using one search box)


I noticed that there are extra maped columns for managed metadata columns (owstaxIdFrequency also has owstaxIdFrequencyx0020Tag, I tried owstaxIdFrequencyx0020Tag="Daily", but it didn't work)



I'm trying to develop a profile navigation system for a Sharepoint 2010 publising site.

The end-user (always anonymous) can select his profile from a list (ie: geek, student, reader, sporty...) and then, I want to show a list with all the publish pages that has a metadata column "profile" with the selected profile.

Can I do this using search server? and how? :)

Thanks in advance.



I have a problem which might be something obvious but I just can't seem to find the answer.

The site administrator in our portal is the only person who can see the entered values in a managed metadata field.
Any other person can still filter the column (one time, next they get page not responding) on the values and it works correctly, but they don't actually see the values in the column.
Someone with contributer permissions can add the term(s) the way he wants, but can't see them in the views, nor in the view/edit item or document screen.

Do I have to activate somekind of feature in order to give my 'normal' users access to read these values, or what could I be missing here?


Via the SharePoint 2010 UI I've created a DocumentLibrary and added a new column of type Managed Metadata. I've associated a TermSet with this column and all works fine. Now I need to create a deployment package in Visual Studio 2010. It is easy enough to create the Document Library. I've followed the below steps

1. Create empty SharePoint 2010 project

2. Added new Empty Element to the project. In the Elements.xml I have

<FieldID="{15712E76-A603-43AB-885E-CE48BD216381}"Type="TaxonomyFieldTypeMulti" Name="DocTags" DisplayName="DocTags" ShowInDisplayForm="TRUE" ShowInEditForm="TRUE" ShowField="Term1033" Required="FALSE" StaticName="DocTagsInternal" Group="NotSure"/>

3. Added ContentType to the project. Added FieldRef elements to the Element.xml

4. Added List Definition From Content Type and associated it with the above Content Type.

5. Created a List Instance of the above List Definition.

6. Build and Deploy.

7. Associate the column with a Term Set.

8. Add Document to the Document Library. I can select a Term from the applicable TermSet, but when I save the document I get:

Failed to get value of the "DocTags" column from the "Managed Metadata" field type control.  See details in log. Exception message: Invalid field name. {00000000-0000-0000-0000-000000000000}.

Not sure what this is telling me, so not really sure how to debug the problem. Any insight on whether I have missed something in CAML or what the error is telling me is greatly appreciated.





all our document lists use Managed Metadata columns. They are required also. 


Sharepoint Workspaces list current values for these columns, but do not allow changing them. Thus effectively making Sharepoint Workspace unusuable, because we can't check-in new documents.


Am I missing something?


Firstly the following is not a problem for users given "Full Control" (and possibly other permission levels might work) at the web application level in central admin.

For any other user with permissions set at site collection level, even "site owners" (full control) , these problems arise.

When adding managed metadata columns to a new document library list, clicking save results in multiple access denied errors getting logged (as seen using UlsViewer) and an exception is raised (sharepoint error page) In existing document library lists managed metadata column headings are displayed in list views but the terms text is not displayed.
This problem shows up even if the logged on user is the term set owner.  "Available for tagging" is enabled, submissions policy is closed.
Looking at http://<the-site-domain>/Lists/TaxonomyHiddenList/AllItems.aspx and then checking list permissions I can see that "All Authenticated Users" has Read permission level.
Integrated windows authentication - NTLM + Claims Based Authentication is the only authentication method used. It's an intranet site. 

Thanks in advance for any help.



We are in process of rolling out our new intranet on SharePoint. Two days away from the launch we have run into a strange problem. We have various custom content types and within that we have custom columns which are managed metadata. The columns are then exposed in various document libraries and users choose appropriate metadata when adding the documents to the library. Everything was working fine, until yesterday all of a sudden we were not able to see any data in the columns which were managed metadata columns. But if we edit the properties of the document we can see the field is populated.

Another strange thing is that if the user has full permission in central admin they can see the metadata in the columns, but anyone else (including site owners) cannot.

Can anyone please shed some light on this and if someone knows how to resolve this?





I'm trying to group a list by a Managed Metadata column, it works fine with my farm admin/site collection admin user account however i can't get it to work for any other user account. I've tried giving one of the other user accounts term store admin but still no luck. With these user accounts all i get is one group which contains all items regardless of what term is selected for the item. The single group displays as an empty term e.g. it looks something like 'MetaData Column: (80)'. However if you look at individual columns you can see what term has been selected.

If it makes any difference I'm experiencing the issue while using an Enterprise Wiki site, I'm trying to group pages in the pages library by the 'Wiki Categories' column. I've set the field to point to a new term set and disabled multiple entries.

Any ideas?


At random times, all our Managed MetaData columns appear greyed out on the Properties screen of individual list/library items.  This usually happens once a week and for about 10 - 15 minutes. 

I'm assuming this is network related.  Our MetaData service runs on our App server, not on our WFE.  But I'm looking for someone to be a bit more specific as to what would cause this.  Is it a certain port?  A certain service stopping?  How excatly does the WFE communicate with the Mgd MetaData service on the APP server?


I like managed metadata in many way, but there´s several things I can´t get "right":

- In a document library I have managed metadata columns. If i filter with one column (say I filter Europe in column Continents) , every other column take´s away unrelevant filtering options (Country column should only show European cuntries) , except the  managed metadata columns, wich show everyting. Why? Can I change that?

- I have a long list of terms in a managed metadata column. When I try to filter that column, I have to press "more" severel times to get the term I want to filter on. Is it posible to see all terms at ones or se more that 20 terms before I have to click on "more"?

Thanks for helping me,



i am unable to edit managed metadata columns in the DataSheetView, i have other columns which are number, text field type which i am able to edit. So the view is not readonly, it is only when i click cell with the managed metadata column i get the readyonly prompt.

Evironment : Sharepoint 2010, Office 2007 and a pissed off customer

Appreciate any help



I am what i am

i am unable to edit managed metadata columns in the DataSheetView, i have other columns which are number, text field type which i am able to edit. So the view is not readonly, it is only when i click cell with the managed metadata column i get the readyonly prompt.

Evironment : Sharepoint 2010, Office 2007 and a pissed off customer

Appreciate any help


I have a problem when trying to copy a value of a managed metadata column from one list to another by a Sharepoint Designer (SPD) Workflow

I have two lists. "Locations" and "Employees". "Locations" has a Content Type integrated that has a Site Column of the type managed metadata named "Geographic Location". This Managed Metadata column describes the geographic location from continent down to the city name. I also have a Content Type for the "Employee" list. This one contains a lookup column "Location Abbreviation" on the title column of the "Locations" list and the same managed metadata column "Geographic Location". Now my Workflow is created to work with the Content Type "Employee" and goes like this:

Set current item:Geographic Location to Locations:Geographic Location (where Current Item:Location Abbreviation equals Locations:Location Abbreviation (Lookup Value (As Text)))

But the workflow always reports "Error occured". The message is:

"The workflow could not update the item, possibly because one or more columns for the item require a different type of information."

But is is very unlikely that this message is useful as both columns use the same Site Column. Do you have any Ideas?


Hello All-

I would like to customize the "new" form on a SharePoint list that has some columns that use managed metadata term sets as options.  Unfortunately, when I do so, I get the message:

"InfoPath cannot generate a form template for the SharePoint list."

The following fields in the SHarePoint list are not supported because of their data type and will not be available in InfoPath Designer:

-MyColumnName (TaxonomyFieldTypeMulti)

This error message seems to be pretty self explanatory, but it boggles my mind that this would be the case.  Can I really not customize my list "new" form in Infopath if I am using columns with managed metadata?  Any workarounds?


<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure