Updating SP2013 refiners using PowerShell

In SharePoint 2010, changes to the refiners were made using the the FilterCategoriesDefinition property of the refiners web part which held an XML blob.  In SharePoint 2013 we instead do this using the SelectedRefinementControlsJson property.  As the name implies, the configuration is now in JSON format.  Conveniently PowerShell 3.0 now includes the ConvertTo- and ConvertFrom-Json…


Mucking with search summaries in SP2013

For a project I’m working on I needed to add some redaction to the hit highlighting summaries of the search results.   If I see anything that looks like a social security number, then replace the first five digits with asterisks. At first this looked somewhat daunting because looking in the item templates, all the action…


Getting the current user’s alias

For a project I’m working on, I needed to know what the logged in user’s account alias was.  Looking around I found examples that would make a ajax call out to the profile page and parse the results.  This seemed like overkill for what I wanted and on a whim I decided to view-source on…


Quick Hits: Using a custom property with hit highlighting

So you have a managed property with SummaryType set to Dynamic and you want to use that in the FAST Search Center but your results show up with <c0> tags instead of highlighted terms?  In the Core Results XSLT, replace the following: <xsl:when test=”hithighlightedsummary[. != ”]”>     <xsl:call-template name=”HitHighlighting”>         <xsl:with-param name=”hh” select=”hithighlightedsummary” />     </xsl:call-template> </xsl:when> with…


Quick Hits: Dealing with managed properties in the search center XSLT

Even though you’ve named your managed property using mixed capitalization, doesn’t mean you can refer to it that way in the Search Core Results web part’s XSLT.  You will need to lowercase them.   See HitHighlightedProperties for an example in the default XSLT. For more, see the official low-down on the Search Core Results web part.