Skip to main content

SharePoint 2010 Web part, which one is used where and when

Image
By

SharePoint 2010 picking the web part depending upon the data coming from  data source.


Comparing view and form web parts
  1. XSLTListViewWebPart : SP list, libraries, external content types
  2. XSLTListFormViewWebPart : from external list
  3. ListViewWebPart:
  4. ListFormWebPart : From a SharePoint  list
  5. DataViewWebPart : n/a - only for backwards compatibility.
  6. DataFormWebPart: Xml, SOAP, REST, Database data source 
  7. InfopathFormWebPart

If you migration your database from 2007 to 2010 then DataViewWebPart gives backwards compatibility.
When you added View in your web part: If data coming from the list like “SP list, libraries, and external content types” then it will display the data in  XSLTListViewWebPart. 
If data coming from the list like “Xml, SOAP, REST, Database data source” then it will display the data in  DataFormWebPart.
When you added View in your web part : If you added the form in your web part and your data coming from the external list then SPD choose XSLTListFormViewWebPart.
If your data coming from the SharePoint list then render the form as a ListFormWebPart.
If want to know which one is used where the really thing is it is not up to us SharePoint Deal with it which web part is used when it depend upon the data source we used.

New Web Part vs Old Web Part

New WebPart
XSLTListViewWebPart is a new type of web Part comes in SharePoint 2010. It gives us a full ribbon supports when we edit the page in browser. Please see the below image.








Old WebPart 
DataFormWebPart gives us less ribbon support when we edit the page in browser. Please See the below image.


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

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more