Tag Info

New answers tagged

1

You should be using REST with SharePoint online. The end point is formatted like this: [site]/_api/search/query?querytext='query' It is far easier to use and requests can be made from many platforms. The documentation is here: https://msdn.microsoft.com/en-us/library/office/jj163876.aspx You can either create a Result Source and use the SourceId ...


2

Goto the search page where you are showing the results Edit the Search results webpart Edit the Query change query to speaker:{searchboxquery}


0

Like you mentioned in the question, MSDN contains the following explanation about the format of search result value for managed metadata field: Data format for Managed Metadata. To query for items tagged with a Managed Metadata field, you have to use the >Unique Identifier for each label. You can find the Unique Identifier for each term in a term ...


0

I have already provided a detailed answer for the same question. Pls refer below Reference Link Any changes to the search controls such as refinement panels or managed properties needs a full crawl either to the entire site or the specific lists/libraries in which the fields were created. also, many time i noticed the preview is not working but it will ...


0

You can refine the search by using the syntax PropertyName:Value. e.g. Title:Bob. You may find all available properties ("Managed Properties") in the search settings, from the CA. Some links: Default managed properties are listed here: https://technet.microsoft.com/en-us/library/jj219630.aspx. See existing properties: ...


1

In SharePoint you can change the default _layouts/OSSSearchResults.aspx to your custom search results page. Kindly follow the below procedures: 1) Add the Search box web part to the page you want 2) Edit the represent page in SPD (2013 SharePoint Designer) 3) Right click on the Search webpart controls, go to tag properties and change your custom search ...


0

I wasn't able to update the property. As a work around I set the Max number of refinement items to 1000. Then, used CSS to hide the refinement items by default and added some JavaScript to the display template to show the first 4 refinement items and append a show more/less button there were more than 4 refinement items. ...


0

I am currently having the same issue with my 2013 search site. here is the article article helped me. I was still having the same error after following the article above. I have added the line below in the web.config <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" /> After this, the ...


0

This does it: $ssa = Get-SPEnterpriseSearchServiceApplication $ssa.SearchCenterUrl = "$SearchSiteURL" #which ends /pages $ssa.Update() No Site Collection settings need to be updated - only if it should display on a different search center.


1

I don't think it is possible to get this information using APIs. This is an admin page, that uses an internal class that eventually executes dbo.proc_GetSlowestPages from the Usage and Health Data Collection Service Application database. You can try querying the database directly, but it is not a "good practice". declare @webApp uniqueidentifier select ...


2

Method 1: Go to Central administration > Manage service applications > Search service application > Crawl rules . Use the belwo configuration and create a crawl rule. Path = ://*/AllItems.aspx Crawl configuration = Exclude all items in this path (check “Exclude complex URLs (URLs that contain question marks – ?)”) Specify authentication = Use the ...


1

For me it excluding AllItems.aspx was a hit and miss. Have a look here http://practicalsharepoint2010.blogspot.com.es/2011/12/search-configuration-best-practices.html maybe it will work for you. When using this approach for some reason on the SP2010 I still had problems with crawling infoPath form libraries.


1

There's multiple possibilities but here's two that are most likely: An issue with loading the URL of the item. Meaning, the item still exists and is there but for some reason you couldn't reach it. When an item is deleted it isn't immediately removed from search results. To keep search results up to date at scheduled times the search system connects to the ...


0

so it turned into an unsolved problem. I have removed the site collection and created it from scratch. It works now. So the problem was specific just for this one site collection and i have no clue why it has happened. Regards


0

After installing Adobe PDF iFilter 11 on SharePoint 2010, we experienced a 7 fold improvement in full scans on our largest content source from 18.5 hours to 2.5 hours. As I understand it, the v. 11 filter has multi-threading enabled, whereas the v.9 filer was running serially. Several "experts" told me that the filter version was not the problem for ...


2

If you're using SharePoint 2013 it should be something like: ({SearchBoxQuery} XRANK(cb=2000) Lastname:{SearchBoxQuery}) XRANK(cb=1000) Firstname:{SearchBoxQuery} Boosting match on last name by 2000, on first name by 1000 and on both by 3000


1

You can actually change the query for osssearchresults.aspx. If you create a new result source on your site collection, apply some filter to it and mark it to be the default result source, then this will be used. But you should note that this will also impact searches in document libraries. So if you create a result source which filters away say word ...


1

You need to map the crawled property for the column to one of the existing RefinableString... managed properties. This is due to a limitation in SharePoint Online where you can not mark additional managed properties as refinable (as you can do on prem) Detailed instructions here: ...


0

There is no "Search Tool" for SharePoint 2007, but there is a built-in Search Engine that has gotten better with each successive version of SharePoint (2010 and 2013). For example, performance and scale have improved significantly.


1

CAML Queries do support checking for Null values (unlike the REST api) and you can use CAML in REST. So you can do something like this: http://somesharepointsite/_api/web/lists/getbytitle('yourlist')/getitems(query=@v1)?@v1={"ViewXml":"<View><Query><Where><IsNull><FieldRef ...


0

Well I've found a solution, not very friendly but works, is based on this article So basically the article says that you need to identify in the query how to include everything that has any value: Text values consist of alphabetical characters (a..z) and numerical characters (0..9) and use a NOT at the beginning to exclude all the possible values... The ...


0

This is very much beyond the scope of Stack Exchange to deal with. Enterprise Content Management is a huge and complex field. There are a great many consultancy companies out there whose entire business model revolves around building Document Management Systems in SharePoint. They never do anything else. The system you describe can be built in sharepoint. ...


0

Sharepoint 2013 cannot consume services from sharepoint 2010. That's mean you can't crawl 2013 content from sp2010 search.


0

SharePoint 2010 requires a user account for crawling content from sites, even if they are configured for Anonymous authentication. SharePoint 2013 resolves this issue by introducing a new approach – Anonymous which eliminate the need of passing an user account and trying to authenticate for crawling content for public-facing web sites with anonymous ...


0

You can also restrict the results based on the Content Type of your pages. I do this quite often on Publishing Sites. ContentType:NewsPage for example.


5

I think @LeopoldLerch is on to the correct approach. Try doing the following Guid siteId = SPContext.Current.Site.ID; SPUserToken systemAccountUserToken = SPContext.Current.Site.SystemAccount.UserToken; HttpContext currentUserContext = HttpContext.Current; if (SPContext.Current != null) HttpContext.Current = null; ...


0

Create a Result Source with following QueryText:(Replace the IDs with the correct list ids) {searchTerms} (ListID:{DDD70E78-941F-45EC-85E0-649B1F6DFE02} OR ListID:{DDD70E78-941F-45EC-85E0-649B1F6DFE02} ) Edit the Search results webpart and Click on Change Query. Select the Result Source you created.


4

Try to delete the current httpcontext before elevating (but do not forget to remember it and set it back like var storedContext = HttpContext.Current; HttpContext.Current = null; <Do something> HttpContext.Current = storedContext; Because it seems to use still your curentUsers Credentials when calling the search service (which it still does in ...


1

I had the problem too. If the document is a PDF, the changes in the crawler-settings won´t help (because the values from the ifilter overrule somehow in the backend). Anyway, my workarount was to create a calculated column in the list, which simply reflects the value of the "Title"-Field. This way you have the expected Value in the search. Then you can ...


2

go to Search Schema and search for the "Title" Managed Property and set the mappings to crawled properties shown in the below image for more details go through Online Search


2

A prerequisite of the AppOnlyContext is the setting in AppManifest: <AppPermissionRequests AllowAppOnlyPolicy="true"> ...snip... </AppPermissionRequests> However, there is a special permission request designed for your scenario. So you may not need AppOnly. <AppPermissionRequest Scope="http://sharepoint/search" ...


3

Wrap the search query in {? {your search query} } format. For your case: {?{SearchTerms} Path:http://archive.myCompany.com } Here's the link to the technet article with explanation on narrowing search results using query transform: ...


0

SPNavigation object has a property named SearchNav. This propery is a SPNavigationNodeCollection. A SPNavigationNodeCollection object contains a Add method with two parameters. Syntax looks like this : public SPNavigationNode Add( SPNavigationNode node, SPNavigationNode previousNode ) The node parameter: The node object (SPNavigationNode) to ...


3

You should rather have result source that would limit results in a web application, and later use that result source in all search result web parts.


0

Create result source with some custom search query Create Result Source with PowerShell Create new page How to create a page in powershell Add search result webpart to page in step 2, and configure it, it needs to use the result source created in step 1 Adding Web part on pages using PowerShell script Important note: In 99.9% of the cases, you'd ...


3

From the site your archiving via Site Settings go to Manage Query Rules (or from Search Service Application page i Central Admin go to Query Rules). On the Manage Query Rules page, select Recently Changed items and push the button New Query Rule. On the Add Query Rule page, enter a rule name, remove the default condition and follow the ling Change ...


0

Thanks a lot Jesus for your quick answer, yes I will definitely asked specific question. I will also go through all the the links you sent. Yes I am an advanced developer with HTML, CSS and kind of Intermediate with JAVASCRIPT, How I am going to use them without designer and no access to the server? can I use a third party editor. Please more detail on ...


0

You are tackling a lot of stuff for your first time out with SharePoint. The answer is YES you can do this. "How" you do it depends on the way your administrators deployed SharePoint and what services they made available to you. First - with Search. Some things do have to be configured in Central Admin, but not everything. More than likely for your ...


3

Those are not log files, it's your actual search index. It is recommended to move the index to it's own drive so that the index (or any other log files) cannot consume all disk space on the C drive. Moving the index means that you need to clone the search topology and then move the clone to another drive. This is kind of a complicated procedure as you have ...



Top 50 recent answers are included