New answers tagged

0

Try the below function. Srch.U.getDisplayNameFromAuthorField(ctx.CurrentItem.EditorOWSUSER) In your case, Srch.U.getDisplayNameFromAuthorField(ctx.CurrentItem.ManagerOWSUSER) I haven't tried it on a custom Person/Group column.


0

The Content Sources defined in the Search Service Application in Central Administration determine what the search engine should index/crawl. In your case, it sounds like you have a content source for your file shares and also the default "Local SharePoint sites" content source. The search engine can continue to index both these sets of content regardless ...


0

I think that you won't be able to avoid an index reset or a re-crawl. I'm not a search expert and have only cloned a search topology once but it seem's that all the search components need to be in a healthy state to be able to clone them, otherwise you would only clone a topology that is still broken and would be stuck with the same problem. SharePoint ...


0

did you ever figure this out? I have a similar situation, and need to understand where the values in PhoneNumber comes from and the magic behind it.


0

search web part uses display template to render result items, you can create you own display template and adjust HTML and CSS, you can also add body of the news item. detail here


0

We want to exclude the contact us and privacy policy links in the navigation from our search results. How do we do that? It’s pretty simple actually. Just put the content that you do not want indexed in a div tag with a class of noindex. Let’s look at the complete HTML of the home page. <html> <head> <title>Super Neat Home ...


0

I see the same behavior in my environment - if I have a hyperlink field, search seems to return the link but not the description. The easiest way to approach this I think is to create a new display template. Copy the Item_TwoLines.html that resides in your Master Page Gallery > Display Templates > Content Web Parts. Be sure to change the ...


0

It appears that you are using the SQL Server name "DBNAME" rather than the actual name of your database server.


3

8 GB is way below the minimum for a standalone SharePoint server in production. See this Technet Article. After you "solve" this issue you will face many more until you add RAM and resources.


0

I had the same problem here. We have an Enterprise Wiki with folders in the Pages library. We also have versioning and content approval activated on this library. The crawler ignored files (Wikipages) in folders which haven't been published/approved yet. After manually setting the Approval status to "Approved" on the folders the crawler found every page in ...


0

Add below code to a content editor webpart in the page where you have the search navigation. Modify the classes and code as needed, <style type='text/css'> .nav1{ background-image: url('image url goes here'); } .nav2{ background-image: url('image url goes here'); } .custom-search-nav{ ...


3

There are some information about this behaviour. See here and here. You can change e.G. the Performance Levels for your crawls. Powershell Cmdlet: Get-SPEnterpriseSearchService | Set-SPEnterpriseSearchService –PerformanceLevel "PartlyReduced" For the setting to take effect do an IISReset or restart the Search Service in Central Admin Performance Level ...


0

ChathuraSam hasnt understood the question as his comment relates to running a search using a managed property that has already been created whereas the question is clearly about creating managed properties using CSOM. Unfortunately I dont have enough reputation to comment. I believe the way to do this (although I havent tried this myself) is with ...


0

The Search Service Application Proxy does probably not exist in the farm. The Search Service Application Proxy is responsible for the communication between the WFE's search web part and the Search Service Application on the application server. Create a new proxy using PowerShell cmdlets: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction ...


1

I have done something similar when the requirement was only search. In our case these were contractors who never had domain credentials. Here is the rough outline of the solution: Create a "Contractor" Content Type based on the Contact Content Type (customize as necessary) and a list using that Content Type. Populate the list with a few items. Crawl the ...


0

In the short term you could set site B to not be indexed (Site Settings | Search and Offline Availability). Then run a full crawl. Another alternative is to remove the site from the main Result Source with a path exclusion like -path:http://path to site/* One other option is to use search results removal in the Search SSA. But it could be very tedious for ...


0

You still need to show these pages that are filtered somehow. Did you have an ordinary list view in mind? If yes, then (provided this is SP2013 we are talking about) you would have to develop a custom web part (it can be just script/content editor web part with html/javascript) which would get the possible refiner values (directly from TermSet or via search ...


0

One way would be to create a new result source and in the query builder you can exclude the paths(s) to those lists/libraries. Something like this: -Path:https://contoso.sharepoint/blog/Lists/Posts/ would exclude blog posts in that list. Then on your results page(s) you would edit the search results webpart and change it's result source to the new one you ...


0

It depends on your crawler settings how much time it takes until your search index is updated again. You can reset your search index manually: Go to the Search Administration page, in the Crawling section, click Index Reset. Verify that the Deactivate search alerts during reset check box is checked, and then click Reset Now.


0

You have to activate the Publishing feature on site parameters. Edit : After lurking, it seems that only the Publishing Infrastructure (site collection parameters) is required to display the HTML file.


0

Contact Office 365 support. If this is happening for all search queries, there won't be much you can do and it may be a service problem.


0

It turned out the crawling account needs read and write access


0

SharePoint 2013 Search works in a different way. There is a crawled property called MetadataExtractorTitle and it has a priority in the managed property mapping. You can follow the following guide to change the priority or re-map crawled properties so that search results return file name instead of title: ...


0

Try changing your query to IsDocument=1 OR ContentType=DocumentSet.


0

In the search SSA you can remove a search result from the index if you have the URL to the item.


0

Comment the below text in Item_CommonHoverPanel_Actions.html' file. <div class="ms-srch-hover-action"> _#= editHmtl =#_ </div>


1

This has always been the case, the initial search gives you a fuzzy result or an approximation. As you page through the result set, the number becomes more and more accurate as it parses through the results. This has functioned in this manner since 2007 version at least and is similar to every search engine you'll find on the web.


3

To make this happen you need to add a Managed Property in your Search Service Application. You find the existing Managed Properties in the Queries and Results section named Search Schema. Type isDocument in the filter section and hit the green button with a white arrow. You should see this: It tells is that the isDocument managed property returns all ...


0

I might have found it now. I changed the values of the property called owstaxIdTaxKeyword for Refine and Sort which were set to No to Yes - active so I can use it as a refiner. Of course only Refine has to be set to use it as a refiner. In there I found the values. Can anybody confirm, that that is the right one for enterprise keywords?


0

You can delete config cache XML files. This is standard procedure when OWSTIMER hang out, incremental/full crawl is running endlessly, HDD space is under 2xRAM and so on. Link from blogs.msdn http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx


0

By restarting "SharePoint search host controller" services on server its working.


3

With KQL it is only possible to query by day ranges. If you want to use something like DateTime.Now you will have to use FQL instead, see link


2

You mapped "ows_AverageRating" to managed property "RefinableDecimal00"? Did you start full crawl after that? Recrawl is important :)


1

to find the recently visited sites, to find top sites etc. We can find it easily by using site.LastItemModifiedDate. using (SPSite siteCollection = new SPSite("siteurl")) { SPWebCollection sites = siteCollection.AllWebs; foreach (SPWeb site in sites) { DateTime dt = ...



Top 50 recent answers are included