SharePoint For Developers

In SharePoint 2013 there are no visual best bets/best bets, keywords replaced with promoted result with Intent based search experience. When condition of query rule trigger based on the rule promoted , result block and result rank applied to the search. why changed to promoted result? When client comes and says, I wanted to display my result i.e. promote my results in SharePoint search center what search analysis replay to client, yes we will add visual best bets or best bets. The really client not understand the technical words best bets and also it not make any sense. Microsoft decided to change the visual best bets to “promoted results”. Query Rules can be created at the Search Service Application, Tenant, Site Collection or Site level. Query rules composed to three components. Condition: When to apply the rules? There are list of condition available, we can create the rule based on the keywords. We can also get the keywords from term store (MMS). For POC p

SharePoint 2010 getting search keyword: we were writing a custom code to get the Search keyword & best bets, we used the FAST Search Proxy. The big bug found & that mentioned below. Special thanks for Mikael Svenson. He already did a lot of research on it. var ssaProxy = (SearchServiceApplicationProxy)SearchServiceApplicationProxy.GetProxy(SPServiceContext.Current); if ( ssaProxy.FASTAdminProxy != null ) Error line { var fastProxy = ssaProxy.FASTAdminProxy; KeywordContext keywordContext = fastProxy.KeywordContext; var searchGroup = (from x in keywordContext.SearchSettingGroups wherex.Name==SPContext.Current.Site.ID.ToString() select x).First();  } Above code was not working, the problem was Fast Search Service Proxy unable to connect with the search service. The FASTAdminProxy reads it’s WCF configuration from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\FASTSearchAdmin\ContentCollectionService\client.config. Servic

Automatically created when site column created and used (the must be stored in the content database using this column). Crawl properties now crated at the site collection level. Earlier only available at the application level. Crawl properties & manage properties created with specific naming convention, as mentioned in the attached link MSDN . Automatically created crawl properties sortable and refinable are turned off and property with text data type. There are list of OOB Manage Properties available at site collection level with different-2 data type start with name Refinable<datatype>00 .. Refinable<datatype>100 to you can use this to make achieve Sorting and refinable by map crawl property one of manage property give it alias.  There is confusion with crawl property, actually in SharePoint 2013 two crawl property created when ever a new site column created and it used. I have created the site column name "MyCustomDate". SharePoint 2013 two

Problem In SharePoint 2010, we do not have OOB web part that get back aggregate results i.e. results more than one site collection. The Content Query Web part displays aggregate list content (data from multiple lists) from within a single site collection. Why not Custom Web part? If the number of site collection is increase, the custom code will cause the issue and this end up with performance or may have a chance for a memory leak. Why Content Search Web part? SharePoint 2013 Content Search web part introduced by the Microsoft to break the site collection boundary problem.Web part displays cross site collection aggregation results. It is OOB solution and fully based on Search(Indexed content) the more often crawl run, the more up to date content. Content Query Web Part (CQWP) Content Search Web Part(CSWP) The Content Query Web Part allows you to display content from single site collection. The Content Search Web Part breaks the site coll

Result Types: Each Search result item render differently. In search result page, whatever renders on the page, it is display on the basis of search result and each control has its own result template like Refiners , Core Result, Search Vertical, Search Box  and Hover card . Each item in a search result page use different " Display Template ". Every web part has a option to set result type template. By default SharePoint 2013 comes up with some default list of template.Apart from the search web part there is another web part called Content search web part(CSWP) has its own result template to render the results. Following are the list of default template that are being used by web part. There are may mores display template but I mentioned the common one.  Search Navigation : Search Results Default Search Box: Default Search Box Core Result (Everyone Search vertical): Default Result Refiner control default : Vertical Content Search WP : Control template:  

Result Source : SharePoint 2013 comes with Result Source, "which is a replacement of SharePoint Scopes and federation locations" . Apply query to transform a corpus subset. In SharePoint 2010, the scopes only are created at the application level to overcome this problem. Result source can be created at Application Level, Site Collection Level and Site Level . Now the every site owner can creates the result source at Application, site collection and site. Site Level Site Collection Level Application Level So site collection result source available to all the sub site, and site can have its own result source. Once it created user create the new Search Vertical and update the core result web part. Following are the steps to create the Result Source. Go to the settings -> Site Settings -> Under Search -> Click to the Result Source -> Click to Add Result Source You need to give the name of the Result Source In Protocol section -> Se

In SharePoint 2013 the best of two Search Engines “SharePoint Search” and “FAST Search Server for SharePoint” was combined to make one Search Engine that would provide greater redundancy and for better scalability. Microsoft did lots of change in search center as compare with new search center. New search center home page the wide text box without any search tabs i.e.  “All site”, “People”  no more exist. Now the tabs are the part of result page in SharePoint 2013. “ Search tabs ” name changes to “search Vertical”. There are 4 Search verticals default available in search center. Everything: Everything vertical comes all results that includes peoples, content, conversations and videos. The search result depends upon the search term example.  Simple term: Display the result; show the preview in hover cards. There is a option to open document view and edit the item directly. Hover card also display the result directly. People name: If a search term contains user name

Search center Error message Sorry, Something went wrong.  correlation id 6661419c-0095-80c5-aec6-75e1cfadfb3f  ULS Log Error Details SharePoint Foundation         DistributedCache               ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache' - Exception 'Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.). Add

Key Points  Search has been available in SharePoint since SharePoint 2001 and all versions till now. SharePoint 2003 Search with some out of box features   MOSS 2007 Search introduce the my sites and people search FAST is both a company and a set of products focused on enterprise information retrieval. FAST and its products were purchased by Microsoft in 2008, but the company was kept essentially intact. FAST continues to develop and support the FAST product line and is working to further integrate it into the Microsoft product set—specifically, into SharePoint SharePoint 2010 two search option available in this product SharePoint 2010 Enterprise Search FS4SP (Fast Search Server for SharePoint 2010) In SharePoint 2013 the best of two Search Engines “SharePoint Search” and “FAST Search Server for SharePoint” was combined to make one Search Engine that would provide greater redundancy and for better scalability.

Analytic Processing component: Analytic processing component now the part of search component. ACP Sends the result to the content processing component to be included in the search result. How many times item have been viewed (by default it store last two week items).Search the item based on what is hot, search by most view count. Historical Information like how many times items has been in all time. Example What is hot Number of times content is viewed Popularity Hot topics in distance thread My previous search Popular result Analyzes the items how users interact with search result events like number of times user search and click the items. Following are the list of event events. Search Analyses Link and anchor text analysis: Analysis the link and anchor from the document processing & improve recall position of on the search result. Click Distance: it calculates the actual distance and click from the authrative site from a specific item, that helps the in t