Hello,
I’m currently doing a migration from SharePoint 2010 to SharePoint 2013 (on-prem) for a client. They indexed a fileshare where they have thousands of documents, all categorized using the “Categories” property for the Office documents.
The “Office:2” crawled property (the one with GUID “d5cdd502-2e9c-101b-9397-08002b2cf9ae”) should contain this property.
So, I created a managed property and mapped it to this “Office:2” crawled property.
I set following options:
– Searchable
– Queryable
– Retrievable
– Allow multiple values (also tried it without multiple values)
– Refinable: Yes (Active)
– Not sortable
– Safe for Anonymous
– Token Normalization
After the creation of the managed property, I kicked off a full crawl.
I added a refiner to my search results page, added the managed property. But I get no results. The refiner does not pop up.
When I modify my managed property and add the other “Office:2” crawled property (which is the document Title), save it, kick off a full crawl and issue a new search query, the refiner pops up with the document title as a value.. but NO category.
The same thing happens with the “Tags” property.
I was able to produce this in 2 complete different SharePoint 2013 environments. Is anyone having the same issue with this property? Is this a bug or am I doing something wrong?
In SP2010, this mapping works! So, this is actually blocking an upgrade for now.
Hello Rhys,
well, no. I had this behaviour checked with a search expert at Microsoft and he experienced the exact same issue. extensive logging for the complete indexing process was examined and the only conclusion he could make was that it has to be a bug. It should work, and it did work in SP2010.
He proposed to raise a case and have it reported as a bug officially. The customer however didn’t want to wait for Microsoft to acknowledge this as a bug and to provide a solution and found a workaround where a custom user property was created via VBScript which contains the metadata from the Categories property. That custom property is indexed properly.
I still have to raise the case though, but there’s the difficulty on who is going to pay the fee for it. My company is not keen on doing this, neither is the customer. If it’s a bug, you get a refund, but seems that both parties are not convinced that Microsoft is going to acknowledge it as a bug.
So, unfortunately… no solution yet. I haven’t checked the fixes of the recent CU’s though. Perhaps it’s fixed by now. I don’t have the time at the moment to look into it any further.
