New answers tagged

0

I fixed this by randomly dragging around some of the divs in the Sharepoint Editor. It's kind of broken now and won't let me add anything else to the page or make any further layout changes without all the webparts becoming corrupt, but it worked!


0

You can add a table on the page and you can add the CEWP in one of the columns. You can fix the width of the column so that the CEWP is exactly below the search box. Good luck!


0

Try if these steps helps you Go to Central Admin -> Manage Service Applications -> Search You will see a link to your Content Sources. If you edit that it will give you the opportunity to setup a schedule for both Full and Incremental indexing You can run a full crawl, once completed you will have results if everything is configured correctly


0

Do you see any error on the screen? Probably a consideration of index reset in Central Admin, and run a full crawl.


0

<# .SYNOPSIS Add managed properties to the Search Service Application. .DESCRIPTION Add managed properties to the Search Service Application. .NOTES File Name: Create-ManagedProperty.ps1 Author : Bart Kuppens Version : 1.0 .PARAMETER ConfigFile Specifies the location and name of the config file which ...


0

Note completely sure if this answers your question, but if you want your Search Results Web Part to only include hits from that site, place your results page in edit mode, and select the "Results" web part for editing, On the right, you will see a button for "Change Query". Typically by default the Query Text is set to {searchboxquery} You just need to ...


1

I would try couple of things. fill the drive space on the your index location.Try to run the indexer Fill the disk space on the Index Database Server. While index is propagation try to reboot the index server. stop the crawler while it is running, do couple of times.


0

Search webparts have an option whether they query synchronously (server-side; the default) or asynchronously (client-side). Still, even if you have multiple asynchronously querying webparts, chance is that users will start complaining about too much delayed loading. Therefore, consider also applying the AD group based caching. Cf. https://support.office.com/...


0

Make sure to map the "ows_MyChoice" value to your managed property and select Multi-value Refinement Item in the refinement options for that refiner.


0

I used css to hide it, that seemed to work okay but I am sure there are better solutions out there. h2.ms-displayInline a.ms-ref-name{ display:none;} Best of luck.


1

Found part of the solution needed for your problem in a blog comment by some guy named Marcus (http://www.sharepointblogs.be/blogs/vandest/archive/2014/03/26/sharepoint-2013-search-open-in-client.aspx): private void EnsureOpenInClient() { UserPreference preference = UserPreference.GetUserPreference(); if (!preference.IsSettingEnabled(UserPreference....


0

The page you show has no results. That left-hand menu contains "contextual" links, so what shows up there is dependent on what is returned in the search results. That's assuming you are using the default page and have not modified the web parts.


0

The solution is https://domain.ltd/_api/search/query?querytext='*'&refinementfilters='write:range(2016-06-13T12:30:00.0000000Z,max,from="ge")'


0

You can use this search to find all the entries in the sites membership lists for the the current user MemberOWSUSER:{User.Name} Then create a custom Search Display template that only displays the site title, and the site url (trimmed from the item url) <html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-...


0

To search on properties in SharePoint, we follow the guide Keyword Query Language (KQL) syntax reference. It states that property restrictions follow this pattern: <Property Name><Property Operator><Property Value> In other words, you search for a title like the following (without white spaces): title:Reference or if they where to ...


0

This is a lookup functionality. You shouldn't confuse that with a search. Search is completely different and will normally not happen in an InfoPath form. Your scenario seems to be about two connected lists. ListA is the list whose form you are customizing with InfoPath. ListB is a list with columns like Name, address, phone number. In the ListA form you ...


0

I found this solution and it works well for me. I do not have the Search Server Express as part of my SP Foundation 2010 installation, so I can't answer whether this will have any affect with it. This is also a jQuery solution, albeit a little longer. This code should be places before the closing tag. <script type="text/javascript" src="https://code....


0

Please check if your Managed meta data column is site column. Because if it is not then it will gives null.


0

Got it working. Here it is: .* Category:"Castle Black" Category:"Kings Landing" Below info is from this link When you use multiple instances of the same property restriction, matches are based on the union of the property restrictions in the KQL query. Matches would include content items authored by John Smith or Jane Smith, as follows: author:"...


0

After you switched to Custom role, you must modify the existing search-topology to move the components to another server. You have to do this via PowerShell, there's no GUI for it. https://technet.microsoft.com/en-us/library/jj862354.aspx


0

As per my experience there is no such rule on which server CA will be provision but as per practice it is basically provisioned on the app server. By default it provision on the 1st server in farm. It's upto you on which server you want to use for CA. I don't see any issue with search server hosting CA


0

If you want all the app related functions on 1 server then your should convert or configure your App server with custom.this is what we had in 2013 everything in one. Now you can configure all the services you want.


0

You need to use the Custom role instead of the Search and Application role.


0

This was accomplished by creating a custom refiner. The code used was: The supporting JavaScript file (My_Filter_InactiveActive_functions.js) was function applyActiveInactiveRefiner(val, refinementCtrl, refinerName, strQuery){ var refiners = {}; refiners[refinerName] = null; refinementCtrl.updateRefiners( refiners ); if (val == 1){ // Active ...


0

There are two ways, to exclude it from SharePoint 2010 Search. SharePoint 2010’s iFilter excludes content inside of a tag. Note that each div nested in that one is re-evaluated for the noindex class, so nested divs may not work as you expect. The product team is considering changing this so that all nested divs are excluded. Read More here about the ...


1

You can make use of REST Search EndPoint and target the list path to search upon Format is http://server/_api/search/query?querytext='MY_SEARCH_TERM+path:"http://server/lists/MyList"'


0

I had Windows Auth turned off... "URL being crawled must be a Windows Authenticated zone." - from here "In order for the SharePoint Search to crawl content we need to configure “Windows Authentication” on at least one zone in the Web Application." - from here


0

Given the Content Source is for a particular FQDN that is not in another Content Source (e.g. an sps3 crawl versus a crawl of the same MySites FQDN), you can either use a hosts file on the crawler to redirect as needed, or use the SiteDataServer property if the Content Source target is a Web Application.


1

For debug purpose, use the broswer console. Identify your REST Call in the console's XHR tab. If red, REST call returned an error: => either query is wrong or SP threw an exception If not red, REST call returned success, even though it has no results: => your query is ok. Right-click to open call in a new tab to see xml results on browser, or ...


0

Unless you're planning a test/development system that would not be used in production, I'd always recommend that the installation is multi-tier. This allows much greater flexibility later should expansion of the solution be required, as you can add an additional server without either spending time separating the SQL and application roles, or ending up with ...


2

Search aggregates all the data across the farm into it's own database. When using the everything vertical from a search page, it is returning the user everything they have access to that matches that term. Search is global. If your site collection is limited in access to a few people, then rest assured that only those people can access the content contained ...


0

It sounds like your search result web part is configured to trim duplicates. Click the gear icon to Edit the page. Click the down arrow on your Search Results web part and select Edit Web part Click the Change Query button Click the Settings tab and select Don't trim duplicates Click OK twice, and save your page


1

Managed Properties are agnostic of Site Collections. So "Wiki Category" does not belong to any site collection. They are bound to Crawled Properties that are either "out of the box" or created as the result of creating Site and List columns and then crawling the content. The only way to ensure that the Wiki Category you seek is from a specific site or site ...


1

Why not just secure the content with a workflow if the status changes? If it's secure it will not show in search. You could also eliminate the content from the default result source, but I'd prefer security.


1

Since it was created on the SSA level, this property refers to multiple site collections. You have another option to create a managed property on the site collection level and map it to that field and you use it on the site collection level.


2

You are missing one approach. If you know all the possible values you can use entity extraction using dictionaries to scan that mp with a multi-value, and have it populate to the WordCustomRefinerX managed properties. If that's not an option, I would go with your options in the order you list them. For the display template option you might want to add logic ...


1

Without knowing how your farm is created and if you have one search site or multiple ones is hard to say. However, if this condition is true in all environments and all site collections, then your approach is the best approach IMO.


1

Look in your crawl rules. Last time I did this it also created a crawl rule to exclude the item from subsequent crawls. just remove the rule.


1

The reason is when they were created, they were added on the SSA (Search Service Application) level not on the site collection level. I found this article very helpful in explaining the differences and limitations


2

I would go for option number two as I did something similar in the past. It requires some development, but in the end, it is easier to maintain. The approach of the article you linked might work, my approach back then was different. In your refiner display template where you loop over all the available refiners, you split the values based on your delimiter. ...


1

Answer: (SharePoint 15.0.4571.1502) If content is re-crawled (eg full crawl, or this item is changed during an incremental crawl) then the item will re-appear in the search results https://technet.microsoft.com/en-au/library/jj219587.aspx does not mention this behaviour. The same behaviour occurs for either of the two remove functions Remove an item from ...


0

According to IFABC Global Web Standards, a unique visitor is an IP address plus a further identifier (such as user name, user agent, or a cookie). If you want to know how many daily unique visitors there are, you should go to the Site Collection Web Analytics Reports – Number of Daily Unique Visitors page. The Summary page is nothing more than a summation of ...


0

Search also has the ability to remove result by URL. You could enter the URL of the canceled page manually and it will be added to the crawl rules and no longer be returned as a result.


0

Maybe you could make a search scope. You would need to make your column a "managed properties" and then add 4 rules for = everything but canceled.


0

You could easily create a new master page without the search control or modify the current master page to remove the out-of-the-box search control and replace it with yours.


1

Looking at your screenshots, your last full crawl took 335 hours, which are about 14 days. That means that when making changes you have to wait about 14 days to be able to search them. Once a crawl started it will run till it finishes, which means that your Incremental Crawls won't even start because the content source is still occupied by a full crawl. Your ...


1

I simply added a sort by KeywordQuery kq = new KeywordQuery(site); kq.SortList.Add("ViewsLifeTime", SortDirection.Descending)


1

I just tested this and while it does index the PDF content it does not index the attached content in a Word document.


0

Not in SharePoint 2010. The indexing was dependent on older iFilter technology. Not on 2013/2016 even though you get "deep linking" for Word and PowerPoint with the Format Handlers, PDF is not included.


1

You cannot "Query a View". You can evaluate the view filter criteria and replicate the query in search. So if you want to filter on a Hashtag simply query the hashtag, like #SharePoint. If you are using other types of metadata you can query that too. The search engine is actually very controllable and predictable. If you are struggling I recommend the ...



Top 50 recent answers are included