Skip to content

edit file for manage-search-schema #4157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: public
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion SharePoint/SharePointOnline/manage-search-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,9 @@ Some managed properties are generated automatically. One example is when you add
The search schema displays the name of auto-generated managed properties and their mappings to crawled properties in grey in the search schema. The search schema doesn't hold the settings of the managed auto-generated managed properties. The settings exist, but they're hidden from the search schema. You can add mappings to other managed properties for the crawled properties, but if you change any other setting, you override the other (hidden) settings and the auto-generated managed property is converted to a regular managed property. If you decide to **change** an auto-generated managed property, review **all** the settings carefully, just as you would when you create a new property manually.

>[!IMPORTANT]
>Auto-generated managed properties are case-sensitive. When accessing auto-generated managed properties, such as through a REST query, verify the casing is correct. If the casing is incorrect, no value will be returned.
>Auto-generated managed properties are case-sensitive. When accessing auto-generated managed properties, such as through a REST query, verify the casing is correct. If the casing is incorrect, no value will be returned.
>
>When the implicit mapping between an auto-generated crawled property and its corresponding auto-generated managed property is modified, such as the auto-generated crawled property is mapped to another explicit managed property or the auto-generated managed property is mapped to another explicit crawled property, the implicit mapping is disrupted. Following a reindex, both the auto-generated crawled property and auto-generated managed property will be removed.

### Refine on managed properties
<a name="__toc351360838"> </a>
Expand Down