Tag Info

Hot answers tagged

1

Filter out all The queryable managed Properties from this list and you have all the default ones: https://technet.microsoft.com/en-us/library/jj219630.aspx Then there are all the autogenerated ones, which you can get my listing all queryable properties in you environment, UI or PowerShell.


1

As filetable stored the data on the fileshare then you can create the content source for file share and crawl the items from that location. how to configure the Search for fileshare read this. http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/07/01/how-to-configure-enterprise-search-to-index-a-file-share.aspx Another option i am thinking may ...


1

As the error suggests, increase the time out value from Search Administration Page Central Administration -> Manage Service Applications -> Search Service Application Farm Search Administration Timeout change value Another option is by changing the IE proxy settings Internet options Connections LAN Settings Uncheck Automatically detect Settings Save. ...


1

I would create a Scope that has these site collections listed as include rules. Then there is no need to remove the existing content source, the scope is just a subset of that index.


1

By utilizing a content enrichment webservice you could pass in the HTML and use eg. HTML Agility Pack to parse it. The write out the values you want to a new managed property. So no crawled properties involved. I'm also a bit curious as to the use case here.


1

The odd time shows up because FAST tries to automatically create 'bins' to put your search results in when you don't tell it exactly how... You said you have many records that have an uploaded date of 21 and 22 August -- FAST figured out the way that it felt like partitioning your results would be to put them into two separate bins with a dividing line ...


1

I think in your refinement panel Xsl, uploaddatedt property is defined as Range Property and not Simple Category. Regarding your first question you already said you have items with that date, So you will get that data only the format that you are getting is weired and to change that you need JavaScript to xsl functions And your next query could be solved ...


1

People results are stored in the SharePoint index, not in the FS4SP index. Hence FQL will not work for people queries. And KQL does do contains. Property:value is contains while Property=value is equals. Author:Mikael will return both "Mikael Svenson" as well as "Mr Mikael". Should work for FirstName as well I believe.



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