Tag Info

Hot answers tagged

3

As Vadim mentioned, you cannot create new managed properties in SPO with Refinable option enabled. However, you can map the crawled property (ows_SiteName) to an already created Managed Property in SPO (RefinableString00) as shown in the below image: You can then set an Alias (SiteTitle) to the RefinableString00 property and use it in search just like ...


2

Found my problem... Instead of a full crawl on the content source, I did an incremental crawl. Silly me... So it worked all along


2

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 = ...


2

Most of the default managed properties in Search are based upon the text datatype. We noticed the same problem when sorting the search results on 'ArticleStartDateOWSDATE'. The sort order was not correct due to the text datatype. We simply solved it by creating a new managed property 'ArticleStartDateOWSDATE2' with the same settings but with the correct ...


1

New custom server columns won't show up as crawled properties until you've populated that column with data and a search has crawled it. So for instance, you create a new list and use your new server columns in that list. You must create a new item in the list and you must populate each new server column field with data (no nulls) and then run a crawl.


1

In addition to the question asked in de comments of the answer. Here is how to convert a datetime to the correct datetime of the timezone of the SharePoint website. SPRegionalSettings regionalSettings = SPContext.Current.RegionalSettings; SPTimeZone timeZone = regionalSettings.TimeZone; // Timezone of the current website DateTime dateFromSearch= ...


1

If I read your question exactly, you want the available crawled properties for a search result. I don't think you can, but you can get the Managed Properties. Mikael wrote up the technique and it still works on perm and there is a workaround in the cloud: http://techmikael.blogspot.no/2014/03/debugging-managed-properties-using.html Essentially there is a ...


1

I've finally dived deep enough to solve my problem. This is according to Microsoft by design with the People Result Web Part, you can use the Core Result Web Part instead. "Apparently, the issue is with the People Results web part. If you remove it and add the Core Results web part instead, point it at the People scope and configure it the same way, it ...


1

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() { ...


1

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.


1

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.



Only top voted, non community-wiki answers of a minimum length are eligible