Tag Info

New answers tagged

0

Try with the content types. Limit the search results for respective content types. Let me know if you have any questions


-1

Open other Site Collection using SharePoint Designer and go to top path and copy the Control_SearchResults.js to same path at your Site Collection that has the problem.


0

Could be the fact that the search engine by default trims duplicate results from a search ( your documents seems like example documents with very similar names and content)


0

Assuming you have jQuery, you could do something like this in your display template: jQuery(STSHtmlDecode(ctx.CurrentItem.yourprop)).text()


0

You can just create a web part page and add the necessary search web parts. Search Box, Refinement and Results are just web parts. The query can be passed on the query string or you can include a link to this page.


0

As far as I know you cannot group the results through REST. I believe the best you can do is sort by and then group the results client side.


0

Had to reset the site definition in order to fix my issue.


1

results.aspx is residing in 15/templates/layouts folder. It appears as if results.aspx is an application page, and therefore contents of this page can't be updated without having to perform deployment. However you can always change master page of an application page P.S. I recommend you start using out of the box search results content page (based on ...


2

How many site collections are we talking about? Why do you have two search service applications? If you want to have a split on search service application's usage, then its better to have it at web application level from a logical architecture perspective. Central admin -> Application Management -> Service Application Association page to identify service ...


1

Each managed property shown in refiner, renders a div with a refinername attribute, which actually defines managed property's html mockup. Below is the sample code: //check the language var language = window.navigator.userLanguage || window.navigator.language; if(language == "en-US"){ //hide/show Managed property's div ...


0

You should use selectproperties as paul suggested After adding it your query should look like below _api/search/query?sourceid='d0aa2c2e%2D7709%2D46f1%2D835a%2D244f483e4b0e'&selectproperties='columnName','columnName2'


0

I got it to work. Mostly thanks to this blog post. I had to create a new Result Type which was sourced from Local People Results and used the Item Display Template I had created earlier. Then I added another Managed property to the Item Display Template. This property is not displayed (in this particular case) it is just needed to invoke this little ...


0

Do an Index Reset followed by a full crawl - if that is an option for you.


0

You can find the information and source code for The Taxonomy Picker control in this post. http://blogs.msdn.com/b/richard_dizeregas_blog/archive/2014/03/13/taxonomy-picker-in-sharepoint-provider-hosted-app.aspx


0

Kannan, I recommend you to create a web part page and drop Search Box, Search Results & Search Refiners web parts on to it. They will be auto connected to each other as there are single web parts on the page by now. Edit the Refiners web part and click on choose refiners and add the managed metadata properties that you have. You many not get the look ...


1

you can update the search results webpart to exclude the word tree by go to the search results page edit the page edit the search result webparts click change query add (and -SharePoint) to exclude the keyword from the search see image below ...


0

I haven't done it, but I have heard that Display Templates are supported in Foundation. You just need to get them from server and drop them into the Master Page Catalog. It's worth a try.


0

The simplest approach is to secure the document to just yourself. Then it will only appear in YOUR results and no one else.


0

If it is just one document in a document library of many files, I would go into Central Admin and create a Search Exclusion rule for the file and it won't appear in the index. It might be listed as Remove Search Results, I only have 2010 on prem atm and 2013 delivered via Office 365 so I can't verify the exact language in Central Admin of 2013 on prem. An ...


1

I encountered the same error a few days ago. Reported it to MS Support and they told me there might be a bug in SharepointOnline which causes the Managed Properties page to default to the incorrect level of site instead of sitecol So avoid using this URL _layouts/15/managedproperty.aspx?property=RefinableString00&level=site And simply use this URL ...


0

I have ended up by maintaining another field with all upper case letters (Which was fine for my business), and used the new field for sorting the results.


0

This problem was solved after multiple support calls with Microsoft. They told me they had other customer support tickets describing the same issue. After a few weeks of back and forth, the office field began to work just as expected. They claimed they didn't do anything on their end but I have my doubts since I had not touched the site. I wish I could post ...


0

What is the build version of your SharePoint installation? Run PowerShell command (Get-SpFarm).BuildVersion to know your SPFarm version If your Farm is not up to date I recommend your to first install all missing CUs and Servcice packs. The latest build version is 15.0.4719.1002 Let me know if you have any questions.


0

It is entirely based on the OCR software that created the PDF (and added the discovered text). In SharePoint 2013 PDFs are indexed natively. In SharePoint 2010 you have to add a third party. You indicate that you are using Adobe, personally I would NEVER use the Adobe PDF iFilter. You will get significantly better results from foxitsoftware.com and their PDF ...


0

If you have a lot of scanned, faxed or other kind of image based content then you will need to carry out a separate OCR step for best results. This will place a hidden layer inside the PDF with all the text inside. Any modern search crawler, including SharePoint's, can then index the content of the documents resulting in many documents, that were previously ...


0

If the PDF file contains images instead of text, i.e. you cannot select the text using a Acrobat Viewer - SharePoint will not be able to index it even with iFilter for Adobe configured. http://blogs.msdn.com/b/priyo/archive/2006/03/02/542208.aspx . He also mentioned the workaround, i.e convert the PDF into Tiff or using the PDF write to convert the ...


0

You´ll have to edit the display-template for the requested item. altough I don´t see a reason why to Display a relative path to "normal" users.


0

Refiners are connected with displayed results. And even when you show all hidden options from refiner, you will get 0 results if you click them. This is because refiner is a concatenation of "Search Query" AND "Refiner value". I guess that you need new box with links only to "Refiner value". You can do this with Search Navigation webpart or create new ...



Top 50 recent answers are included