Skip to main content

SharePoint 2013 why content Search Web part?

Image
By
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 collection boundary problems. Content available depend upon your search scope.
Use List or libraries as a data Source to display results.
Use search as data source to display contents.
Use XSLT to render the result.
Use Search Template to display the result.
Content Always up to date.
More often you crawl, the more up to date content.
Content always available, it is not depend up the search service. 
Content not available if search server down.
Customize required to overrides the content query web part.
Customize the result required a content enrichment web service during document processing.
To change the content representation required to modify the XSLT
To customized the content representation, required to create the custom display template.
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

Send Email using SharePoint Rest API

By
We have a requirement to send email vai SharePoint Rest API. We dig and find the below solution to send email using SharePoint API. Point Must be remember End point " /_api/SP.Utilities.Utility.SendEmail " end point to send email.  In JSON __metadata we used the type " SP.Utilities.EmailProperties ". The User / Group must have a read permission for particular site. where we placed this site code. JS Dependency  JQuery Code URL:  https://gist.github.com/BasantPandey/05189832546f2c6cc0bd008fcfec3264#file-sharepointsendemail-js Code  var Email = function (){ // Email Either email groupname or email address var from = ' abc.yahoo.com ' , to = ' abc.yahoo.com ' , cc = ' abc.yahoo.com ' , subject = ' My Email Subject ' ; this . options = this . options || {}; this . options [ ' fromEmail ' ] = this . options [ ' fromEmail ' ] || {}; this . options [ ' toEmail ...
Post a Comment
Read more