Tag Info

Hot answers tagged

4

No, not by default. You need to do a workaround like this: Data on the app web is not crawled by the search indexers, so custom data must be deployed remotely or in the host web. This applies to all apps for SharePoint, but we note it here because apps intended for anonymous access often require search functionality. Reference: How to: Create apps for ...


3

The real answer here is to create a result source where you for "Type" choose "People Search Results". You don't need to add ContentClass=urn:content-class:SPSPeople For example: {?({searchTerms})} {?OR (({searchTerms}) spcontenttype:contact)} will give people + results of contenttype=Contact When testing this in the query wizard it will append ...


2

Here is a way of changing it with powershell (still needs to be done per webpart though..) # Author: Mikael Svenson - @mikaelsvenson # Company: Puzzlepart # Date: December, 2013 # Reference: http://www.sharepointnutsandbolts.com/2013/12/Using-CSOM-in-PowerShell-scripts-with-Office365.html # replace these details (also consider using Get-Credential to enter ...


2

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

In SharePoint fields have display names and internal names. Created By or Modified By are display names of fields. Internal names are used when creating queries. Author is the internal name of Created By field and Editor is the internal name of Modified By field. UPDATE One way to check the internal name of a field from SharePoint UI is to go into List ...


1

Refinement occurs AFTER the query. What you are attempting is more like the Advanced Search offered in SharePoint. The end user can select a link for "Advanced Search" and be taken to Advanced.aspx in the search center. The Advanced Search page contains a web part that you can alter to meet your needs. I would start with that to see if you can get your ...


1

Crawling SharePoint is typically done by SPS3 protocol (if specified in search source). This is default way for crawling and indexing SP. It does not rely on the content of default.aspx or any other SP page. It uses web services to analyze SP structure for crawling and indexing contained data. So excluding AllItems.aspx or Default.aspx does not affect ...


1

It wont affect the documents being crawled, only the allitems.aspx will not be crawled. If you are excluding Allitems.aspx using crawl rules, then after setting the rule, reset the index and do a full crawl. Resetting index and full crawl is not needed if you do it by Search Result webpart properties, as part of query option {searchboxquery} ...


1

As always, all the strange issues have simple answer, for on of the list where i was able to search 20 items, I noticed that we have "Content Approval" setting was turned on. Hence all the items were considered as "Draft" and visible only to people with admin privileges. Since i have full access on the farm I was able to see everything. Another thing ...


1

We eventually got search working by clearing the configuration cache. Here is the article with detailed information about this process: Perform the below steps on all the servers in the farm. Stop the Timer service. Start -> services.msc -> SharePoint Timer Service (SPTimerV4) -> Stop Browse to %SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID ...


1

Check the result sources: People: {?{searchTerms} ContentClass=urn:content-class:SPSPeople} Local Content: {?{searchTerms} -ContentClass=urn:content-class:SPSPeople} For local the minus in front of the content class excludes the people results. For people the contentclass excludes your list. Create a copy of the people result, add your custom list ...


1

There are a couple of way to do this. You may try to Manage all of the rich text fields (promote them from crawled properties to managed properties and then do a full crawl). Then reference the fields in your search query. The problem you may find is that you won't actually get all of the info from the field (if there is a lot of data in the field you may ...


1

You can just use a "Advanced Query Text Match" and choose "Query contains one of these phrases". You don't need RegEx. (I mean, you CAN, but you don't have to.) I blogged this the other day: http://www.ableblue.com/blog/archive/2014/03/31/better-best-bets/


1

You can use the automatically created crawled properties but there are some rules you need to follow unless you want to write your own code. The details are outlined here: http://technet.microsoft.com/en-us/library/jj679902(v=office.15).aspx Two point that I think are important: "When you search for a crawled property, you may find two crawled ...


1

Have a look at troubleshooting the hidden taxonomy list on the site throwing the error. This post mentions that may be the root of the error. You may be able to open some of the documents that use broken values and then save them back. http://share-my-point-2010.blogspot.com/2012/09/error-from-sharepoint-site-index-was.html There is also a repair script ...


1

Should your query type be STRING and not MSSQLFT (SQL Syntax is deprecated). I assume you are using SharePoint 2010. For the KQL, change the query to something like write:02/27/2014..05/27/2014 or write>02/27/2014 AND write<05/27/2014 (either should work). Did you know you can also use cool variables like write:"last month" according to Michael ...


1

Adobe PDF iFilter 11 installation instructions: http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/Acrobat_Reader_IFilter_configuration.pdf It's using the same GUID as previous versions: {E8978DA6-047F-4E3D-9C78-CDBE46041603} I doubt it will greatly improve the crawl performance. I'd rather take a look at the Foxit PDF iFilter ...


1

The list title is available in the Title property of for example a view on the list (AllItems.aspx). My research so far show that the Title managed property of AllItems include both the site and list name separated by a -. So, there is no way to get the list title as part of a list items managed properties today, without adding a column to the list ...


1

Try the following. Set "Which source should results match?" to "All Sources". Under "Show more conditions", select ContentSource contains any of (Your Content Source Name). Also ensure your display template is selected at the bottom.



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