How to force an item to be removed from the index immediately with FAST Search for SharePoint
There are way to obtain the Item ID (or ssic://<id>) using the Crawl Logs, so here in this post I will show how to obtain it directly through the Search Center. This will also be a neat way to show you how to get the raw XML for the search results, which is very helpful when you are troubleshooting issues with your search results (such as to confirm that some property is being returned properly).The first thing you need to do is execute a query on SharePoint site that returns the item you want to remove from the index. Next you will need to customize the Search Core Results Web Part with this XSL (obtained from this MSDN article on how to get XML search results)
These are the detailed steps to configure the Search Core Results Web Part to
use this XSL as well as return the additional property we need to run the
command to remove the item from the index:
|
2) Click to open the XSL Editor and replace all the contents of the XSL entered there with the XSL listed below:
<? xml version = "1.0" encoding = "UTF-8" ?> < xsl:stylesheet version = "1.0" xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" > < xsl:output method = "xml" version = "1.0" encoding = "UTF-8" indent = "yes" /> < xsl:template match = "/" > < xmp >< xsl:copy-of select = "*" /></ xmp > </ xsl:template > </ xsl:stylesheet >
|
3) Edit the Fetched Properties parameter, adding the following entry right after the opening <Columns> tag (and before the </Columns> tag): <Column Name=”contentid”/>
4) Confirm the changes to the web part, save the page and check the new output of your search results page showing the full XML with the additional properties you wanted
Now, login to FAST server and open Powershell for FAST with the contentid in hands we can execute the command to remove this item from the index:
docpush -c sp -U -d ssic://4583And with that you have a way to remove items from the FAST Search for SharePoint index whenever you need. It does take some work, but at least now you have a way to accomplish that.
No comments:
Post a Comment