Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I am trying to use a content query web part on SharePoint 2010 Server and filter on site columns of type "Managed Metadata". These columns do not show up int the available columns drop down in the filter configuration. Does anyone know why? Is this a bug/by design?

share|improve this question
add comment

6 Answers

up vote 1 down vote accepted

I finally managed to send the Managed Metadata fields to my XSLT by setting them in the property DataMappings and DataMappingViewFields. Setting them in CommonViewFields did not work. I also have to define ListUrl AND ListName.
Although I don't need the GUID of the list using this method, I still need the GUID for the Managed Metadata fields.

So the essential pieces would be like this:

<property name="WebUrl" type="string">~sitecolection/someplace/myweb</property>
<property name="ListUrl" type="string">~sitecolection/someplace/myweb</property>
<property name="ListName" type="string">Pages</property>
<property name="DataMappings" type="string">NameUsedInXSLT:{guid-that-belongs-to-managed-metadata-field},NameOfManagedMetadataField,TaxonomyFieldMulti;</property>
<property name="DataMappingViewFields" type="string">{guid-that-belongs-to-managed-metadata-field},TaxonomyFieldTypeMulti;</property>

And that's it.
I didn't find any way to not use guid for Managed Metadata fields.
And you can still specify other non-Managed-Metadata-columns you use in the property CommonViewFields

share|improve this answer
    
which field specifically are we talking about when we say " the GUID for the Managed Metadata fields"? I've fired up SharePoint Manager and located the field on the relevant list...is it: Id LookupWebId SspId TermSetID TextField –  user5534 Dec 8 '11 at 6:31
add comment

I'm not sure, but I'm pretty sure that the Managed Metadata column is sort of like the Multiple Choice column type - that it can store multiple values, and thus can't be filtered in the CQWP.

(If you think about it, the database query would have to match on only part of the value that's serialized into the database field, and hence it would be REALLY slow)

I think... ...can't say that I've checked.

share|improve this answer
    
Thanks! that makes sense. I hope someone can confirm. –  Anonymous Jun 7 '10 at 19:27
add comment

Hmm nope I have used Managed Metadata columns as part of CQWP numerous times. Its actually one of the new features of the CQWP.

I think that you might have something incorrect with the query in the CQWP, do you see all the other columns because it seems strange that you cant see Managed Metadata columns.

Cheers

share|improve this answer
    
Thanks for your response. In the filter settings we selected our custom content type which has managed metadata columns associated with it. It also occurs if we select "All Columns". Not sure what is wrong here. –  Anonymous Jun 8 '10 at 20:23
add comment

I was able to show the "managed metadata" column in the filter dropdown when I specified a specific library/list.

It doesn't show up when any of the following source is selected which is frustrating, alright.

  • Show items from all sites
  • Show items from the following sites and all subsites
share|improve this answer
    
By the way, do you know of a way to list child dependencies for a particular content type? –  Anonymous Jul 8 '10 at 16:32
    
This seems to be true. Do I have to specify ListGuid, or can I use ListUrl when pointing to a list for pages? And must I specify Guid for the managed metadata-fields as well (in CommonFields)? –  eirikb Jul 28 '10 at 9:48
add comment

Managed metadata columns can be used in the CQWP till they are not selected to allow multiple values when you define then under site columns. Once you have selected them to allow multiple values , CQWP will treat them as a Mulitple Choice column type and will not display them under the Allowed Columns dropdown...

share|improve this answer
add comment

I always have my MM Site Columns as not Multi Valued, but in the Library where they are used, I make it Multi-Valued. So CQWP always works in that scenario when picking values

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.