Identify unmapped crawled properties by using Windows PowerShell (FAST Search Server 2010 for SharePoint)
Applies to: FAST Search Server 2010
Topic Last Modified: 2011-02-09
Not all new crawled properties are automatically assigned a managed property mapping and made available for searching. If the MapToContents property on the category is set to $false, all new crawled properties discovered for that category will not be mapped into the default full-text index and made available for searching. Use the following procedure to look up unmapped and potentially new crawled properties.
-
Verify that you meet the following minimum requirements: You are a member of the FASTSearchAdministrators local group on the computer where FAST Search Server 2010 for SharePoint is installed.
-
On the Start menu, click All Programs.
-
Click Microsoft FAST Search Server 2010 for SharePoint.
-
Click Microsoft FAST Search Server 2010 for SharePoint shell.
-
At the Windows PowerShell command prompt, type the following command to display all categories:
Get-FASTSearchMetadataCategory >> CrawledPropertyCount DiscoverNewProperties MapToContents Name >> 133 True True SharePoint >> 15 True True Mail >> 25 True True Office >> 54 True True Basic >> 52 True True Web >> 15 True True OutsideIn >> 10 False False MESG Lingustics >> 10 True False Enterprise Crawler >> 3 False False Format Information >> 7 True False Managed Metadata >> 0 True True JDBC >> 19 True True Lotus Notes >> 0 True False People >> 3 True False Notes >> 0 True True Business Data >> 1 False False FAST Search Connector
-
Get the category:
$category = Get-FASTSearchMetadataCategory -Name "<CategoryName>"
Where:
-
<CategoryName> is the name of the category from which you want to display unmapped crawled properties, for example Notes.
-
-
Get the list of unmapped crawled properties for the category:
$unmappedCPs = $category.GetUnmappedCrawledProperties()
-
Display the list:
$unmappedCPs