Saturday 8 September 2012

Sites developed using SharePoint

Content Type Hub Feature

Tips On Content Type Hub Feature (Pros / Cons)
  • Site columns do not support phased/incremental deployment. Hence always try to create all the site columns required in all phases in first deployment of the application. It makes the publisher/subscriber functionality into a less error prone.
  • Always Remember Don’t create site columns programmatically, It is an error prone and it is not recommended way of creating site columns
  • Content type Hub feature is one of the unstable feature of sharepoint 2010, so be careful of taking this path
  • You might be experiencing errors at the following areas
    • Consumer site's Content Type Column ordering
    • Consumer site's Content Type Column hide/visible
    • Consumer site's newly added Content Type Column has not been consumed even after completion of Subscriber timer job
    •  
    • Consumer site's deleted Content Type Column has not been removed from content types even after completion of Subscriber timer job

PowerShell World

  • Easy Way to loop through the sharepoint 2010 custom lists/libraries and its content types using powershell script.

 **********  **********  **********  **********  **********  **********  **********
Remove-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
# Site declaration
set-variable -option constant -name url     -value "http://<<Site collection URL>>/Sites/Sitename"      
$site=    new-object Microsoft.SharePoint.SPSite($url)
                          
# loop through all site in the site collection, 
# then through all lists / libraries in that site (filtering out everything but actual doc libs 

foreach($web in $site.AllWebs)
{
        Write-Host ($web.Name + " - Site Name ********** Starts Here ")
       
# INT Site Processing Starts here
   
    if ($web.Name -eq "<<SubSite Name>>")
    {
        # 1 loop
        $site.AllWebs | Foreach-Object { 
        # 2 loop
          $_.Lists | Where { ($_.BaseType -eq "DocumentLibrary") -and ($_.BaseTemplate -notmatch "Catalog") } | Foreach-Object {
         
                        # Individual Library level Starts here
                         
                          if ($_.Title -eq "<<Library Name>>")
                          {
                               Write-Host (" <<Library Name>> Library " + $_.Title + " - " + $_.BaseType + " - " + $_.BaseTemplate )
                          }
                         
                          if ($_.Title -eq "<<Library Name>>")
                          {
                           Write-Host (" <<Library Name>> Library " + $_.Title + " - " + $_.BaseType + " - " + $_.BaseTemplate )
                          }
                         
         
          # Ends here
               # $_.Update()
              } # 2 Loop ends here
             
            } # 1 Loop Ends here
       } # If condition of INT Site Processing Ends Here

# foreach($web in $site.AllWebs)  Ends here        
}
 ********** ********** ********** ********** ********** ********** **********

Managed Metadata Service Application


Managed Metadata Service Application
  • Term Store
  • Content type syndication
  • SharePoint Metadata Manager
  • Term & keyword field support in Office 2010 clients
  • Import of Managed Metadata data from another taxonomy store
  • Term & keyword integration in Office 2010 clients via Backstage
  • New managed metadata field type bound to a term set