SharePoint 2013 gives us a lot of new options when it comes to creating new Managed Properties for Search. Luckily there’s only a single Search Service Application to deal with with SP2013 and the process in UI is fairly straightforward.
In your Search Service Application, find the “Search Schema” in the left hand navigation under Queries and Results. That will take you instantly to the list of managed properties. Find “New Managed Property”.
Give your property a useful name, and if you choose, a useful description. Give your property the proper type. In FS4SP and SharePoint Search 2010, a mismatched property type could cause your searches to completely blow up. So far I’ve been diligent as to map everything correctly, but it may still be an issue in SP13. I will post and update when (and I will) break search.
Scrolling down, you can set specifics for your new managed property.
-Searchable – I’m guessing this is should be a must!
– Advanced Searchable Settings – Change the weight and which full-text index the property belongs.
-Queryable – if you need to do fielded search on this managed property
-Retrievable – if you need to show the contents in the body of the search results
-Allow Multiple Values- if this is a multivalue field.
-Refinable – if you want to make a refiner out of this field
-Sortable – if you want to sort by this result.
-Token Normalization – Enable to return results independent of letter casing and diacritics used in the query
-Complete Matching – Match the EXACT field value
-Alias – If you have a beast of a property name (I _AM_AN_AWESOME_MANAGED_PROPERTY_NAME), and want to have something shorter so people can do fielded searches on it.
– Custom Entity Extraction – Custom extraction dictionaries
After you set those settings, map your crawled property(ies) next. I have not tested Company or Custom Entity Extractions yet.
In PowerShell, if you set –Queryable $true, the following is also true:
– Searchable = true
– Retrievable = true
-Token Normalization = true
We take you through 10 best practices, considerations, and suggestions that can enrich your Microsoft Teams deployment and ensure both end-user adoption and engagement.
The following are set to false:
– Allow Multiple Values (HasMultipleValues) = false
– Refiner = false
-Sortable = false
-Complete Matching = false
-Alias = false (You can create an alias using the .AddAlias(“ALIAS”) in PowerShell)