{"id":87,"date":"2020-02-17T16:11:42","date_gmt":"2020-02-17T15:11:42","guid":{"rendered":"https:\/\/help.metashare.com\/metashare-help-admin-manual-how-to-configure-managed-properties\/"},"modified":"2025-08-12T09:56:21","modified_gmt":"2025-08-12T07:56:21","slug":"how-to-configure-managed-properties","status":"publish","type":"page","link":"https:\/\/help.metashare.com\/en\/metashare\/faq\/search\/how-to-configure-managed-properties\/","title":{"rendered":"How to configure managed properties?"},"content":{"rendered":"\n

Managed properties are values that can be used in search queries, when searching on specific metadata properties, and they can be shown as search refiners\/filters, in the search results page. They are mapped to crawled properties that are used for indexing the content. Follow the following steps to configure your managed properties:<\/p>\n\n\n\n

    \n
  1. Open SharePoint’s managed properties’ page:\n
      \n
    1. Go to MetaShare’s start page<\/a>.<\/li>\n\n\n\n
    2. Click on the “Settings<\/a>” function in the top bar:
      \"MetaShare's<\/li>\n\n\n\n
    3. Click on “Search properties” in MetaShare settings’ left navigation menu and then on “managed properties” link, on the top of the page:
      \"How<\/li>\n<\/ol>\n<\/li>\n\n\n\n
    4. For each of the site columns, that you want to be able to refine\/filter on and also search on, using custom aliases, e.g. documenttype:policy, do the following:\n
        \n
      1. There are pre-created managed properties that are not mapped to any crawled properties. These properties’ names start with Refinable and are searched for under the “Managed Properties” tab:<\/span>
        \"Search\n
          \n
        1. for text based columns (managed metadata, people or groups, choice or single line of text), search for “RefinableString”. In MetaShare, the filter will show each and one of the text values and look something like this:<\/span>
          \"Text<\/li>\n\n\n\n
        2. for date columns, search for “RefinableDate”. In MetaShare, the filter will show ranges of dates and look something like this:
          \"Date<\/li>\n\n\n\n
        3. for number columns, search for “RefinableInt”. In MetaShare, the filter will show ranges of numbers and look something like this:
          \"Number<\/li>\n<\/ol>\n<\/li>\n\n\n\n
        4. Click on a managed property with no “Mapped Crawled Properties”:
          \"Managed<\/li>\n\n\n\n
        5. To be able to search using the document property, e.g. keyword:gdpr, provide an “Alias” for the property:
          \"Provide\n
            \n
          1. Aliases may not contain spaces, so the alias for “document type” could be “DocumentType”.<\/li>\n\n\n\n
          2. Aliases may contain international characters such as \u00e5, \u00e4, \u00f6, etc.<\/li>\n\n\n\n
          3. If multiple aliases are to be provided separate them with semicolon (;) without any spaces, as the example above.<\/li>\n\n\n\n
          4. Aliases need to be unique in the search schema, so an alias cannot be used in multiple managed properties.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
          5. Click on “Add a Mapping”:
            \"Add<\/li>\n\n\n\n
          6. Search for the site column’s internal name<\/a>:
            \"Search\n
              \n
            1. If you can\u2019t find your crawled property, it is possible that it hasn\u2019t been created yet. This could be because no document has yet been tagged on the specific metadata. Note that a new search crawl starts every 15 minutes. If your workspaces are configured for item draft security<\/a>, please note that these documents first need to be published before they will be crawled by SharePoint and before SharePoint creates a crawled property for these site columns.<\/li>\n\n\n\n
            2. Depending on property type chose the appropriate one:\n