SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're trying to create a seach query that grabs a content type based on a taxonomy field added to our custom Publishing Page content type. We seem to be having one of two issues:

  1. We don't know how to call a field that has a space. We've been using the internal name Department:{Page.EH_x0020_Department} and also tried the display name Department:{Page.EH Department}. Neither work, nor does inserting %20 between the two.

  2. We just don't know how to call a managed-metadata page field. If we copy/paste the term we want returned into the title of the page {Page.Title}, the query works. Are we missing something that is extra for managed metadata fields?

I couldn't find anything aside from the basics on Google, I appreciate any help that can be given.

share|improve this question
I have gotten confirmation from Microsoft that this is indeed a bug with SharePoint 2013. I will update this with any solution I hear back from them. – EHorodyski May 8 '13 at 13:06

Certainly late to the game here, but for the benefit of anyone else that stumbles across this page, you can use the following to reference a Managed Metadata column called MMSFieldName in the CSWP:


The reason for this is that the token is transformed to the GUID (TaxID) rather than the plain-text label value. In the above owstaxIdMMSFieldName would be the crawled property name - you cannot use a managed property for this purpose.

share|improve this answer

It may well be a bug, but for fellow travellers, I found this in TechNet.

Dealing with spaces in values

Search queries use the space character to tokenize query values issued by users. When a query variable is expanded to a value that contains a space, the complete value is enclosed in double quotations. For example, for the query author:{User}, the expanded value becomes author:"John Smith".

If you don't want the value to be enclosed with double quotations — for example, when concatenating multiple values — you can use the escape character in the query variable. For example: customProperty:”{\User.Name};{\User.ZipCode}” would become customProperty:”John Smith;98109”.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.