Tag Info

You can use PowerShell to create a Crawled property and a managed property. You can use the following code to create and map the properties Param( [string]$crawledProp, [string]$managedProp, [int] $typeManagedProp ) # TypemanagedProp 1 = Text 2 = Integer 3 = Decimal 4 = DateTime 5 = YesNo 6 = Binary 7 = Double $snapin = ...

You can use SPSecurity.RunWithElevatedPrivileges. this is a delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool. For example: SPSecurity.RunWithElevatedPrivileges(delegate() { ...

Steffen, you could do the following: do a webservice call to the search service, query each domain/username and retrieve it's displayname. Replace the refiner display values with the returned displaynames. But I do think that the displayname should be indexed, too. you might investigate it a bit.

Did you add the column in the core results webpart properties? There is a property where it's an xml document which says which columns to return in the search results. Without your column being in that xml, that column won't appear in the data sent to the XSLT, and thus, you just getting an empty value in the XSLT transformation.