3

I have a multi valued managed metadata property in office 365 called products and it only generated 2 crawled properties owstaxidProducts and Products. I tried to associate both to refinablestring01 and see some gibberish(seems like some guid and some value) in the refinement panel. Please help.

Improve this question
3
  • Why should not owstaxidProducts be enough as a refiner?
    – Robert Lindgren
    Nov 7, 2013 at 7:42
  • 1
    I'll try to replicate this in my tennant. I need to ask the basics though. Is your refiner Multi attribute set? (It should be by default.) When you added your refiner to the Refinement Web part, did you use the Multi-value Refinement Item display template?
    – Matthew McDermott
    Nov 9, 2013 at 13:32
  • I am also having this same problem adding refiners using Managed Meta-Data on Office 365 / Sharepoint Online. After associating with refineablestring01, it becomes available in the Refiners Web-Part but displays as "GPO|#8516df41-etcetc". So a GUID rather than the description. The refiners actually work perfectly to filter the search results but until i can get it to display the Title is worthless to me. The suggestion of trying the Multi attribute set template simply gives check boxes and allows multiple selection but does not help cleaning up the display of the Title. Any pointers releating
    – user21015
    Nov 26, 2013 at 1:47

3 Answers 3

Reset to default
3

When mapping a crawled property to a refinable managed property, you should select the crawled property with the ows_ prefix!

Don't forget to run the full crawl afterwards

Improve this answer
1
  • Yep, that should be it. At least on premise this is usually the case :)
    – Robert Lindgren
    Jan 24, 2014 at 5:14
2

In case you'd like to get a proper text displayed as a refinable string, you'd need to map ows_NameofYourColumn to a Refinablestring predefined value.

SharePoint crawl is creating two properties for managed metadata columns: ows_ and ows_taxid. The former is a pure text representation. While the later is a value of the managed metadata field with GUID and type associated.

If you'd have initially picked up the wrong mapping and changed it to the correct one later on, you'd need to wait a bit for Search crawler to pickup the correct mapping.

Here is a nice article covering this scenario. It is valid for SharePoint 2013 and SharePoint Online.

Improve this answer
-2

You may get help from this link Search Refiners with Managed Metadata

Improve this answer
2
  • 1
    It looks like this post is for SharePoint 2010. The question is about SharePoint 2013 in Office 365. Refinement has changed considerably in the new version.
    – Matthew McDermott
    Nov 9, 2013 at 13:08
  • Please don’t add just a link as answer to a question. If the link is broken, the answer you provided will not be useful for future visitors. Provide an answer of your own and use the link as reference. If needed you can block quote the content from your link. More information is found in our help center, especially How do I write a good answer
    – Benny Skogberg ♦
    Jan 9, 2014 at 9:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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