Tag Info

Hot answers tagged

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; ...


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 ...


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 ...


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: ...


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.


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 ...


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" ...


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


2

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


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

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 ...


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 ...


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 ...


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: ...


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 ...


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 ...


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

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 ...



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