1

In quite a few pages on Microsoft TechNet describing the new search schemas for SharePoint 2013, they use the phrase, unused managed property. It's not entirely clear what that means in this context. If tenants and site collections can have their own search schemas now, does that not allow for their own definitions of managed properties? Does each property name have to be unique across all schemas?

Reference

Improve this question
2
  • Suggestions for improving my questions? I've still got a few with 0 answers to accept.
    – Tom Resing
    Commented Dec 21, 2012 at 17:16
  • It's the first time it's been questioned to me. Overall, I haven't really worried about it. Every once in awhile, I try to think of a question that's not readily answered and sometimes, there may be no known good answer or I move on to solving the issue another way with really finding a solution to the question.
    – Tom Resing
    Commented Dec 21, 2012 at 17:51

1 Answer 1

Reset to default
1

At the bottom of Manage the search schema in SharePoint Server 2013, it describes the use of these "unused managed properties". It states:

The following table provides an overview of the default unused managed properties that you can reuse and rename using an Alias.

and continues with a table of managed properties that are shipped OOTB, but that are not used in the 600 some odd managed properties.

Even though multi-tenancy environments now have their own search settings, you are unable to create a new managed property (or perhaps only certain types? I don't have the ability to confirm this). Instead the "unused managed properties" can be repurposed as search schemas in a multi-tenancy environment.

Helge Solheim describes this in his blog post that you linked:

4) The new multiple index schema mechanism with index schemas on tenant and site collection level (covered by the other blog post). To accomodate this without making things too expensive these additional schemas cannot create "expensive managed properties". However, they can reuse existing managed properties, and we ship with a number of default unused managed properties named RefinableString22 etc. There are 270 of these managed properties in total, if I managed to get the math right.

So MSFT provides these pre-configured "unused managed properties" for this purpose.

Hope this helps.

Improve this answer
2
  • Ah, "unable to create a new managed property" is the key. Thanks for reading through all of that an pointing out what I was missing. This seems like a slightly odd way of implementing this to me, but at least it allows for some way to used managed properties in multi-tenancy.
    – Tom Resing
    Commented Dec 21, 2012 at 17:48
  • Not a problem, it helps me to learn more myself, plus it documents the question and answer for anyone in the future looking for an answer to the same question. The implementation is their way to prevent the search schemas from becoming too taxing on the server's resources. It's to force multi-tenancy environments to be good SharePoint citizens and play well with others.
    – RJ Cuthbertson
    Commented Dec 21, 2012 at 17:51

Your Answer

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

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