SharePoint 2013 Base Types , List Template & Definitions Id, CT id

list of the IDs of the most common Base Types, List Definitions and Content Types. Especially useful if you’re writing CAML definitions of Lists, List Instances, or Content Types. Here are the lists I’ve gleaned from MSDN.
Base Types These Base Types come from the SPBaseType enumeration. Base TypeIDCustom List0Document Library1Not used2Obsolete. Use 0 for discussion boards.3Surveys4Issues List5
List Definitions These List Definitions come from the SPListTemplateType enumeration.

SharePoint XSN provisionning with WSP

it's not very simple to package a form xsn in the wsp solution, specialy if you want to do a provisionning.

You probably tried to use something like: 1<elements xmlns="">
2<module name="DefaultForms" rootwebonly="FALSE" url="Lists/Forms">
3<file path="DefaultForms\TestForm.xsn" type="GhostableInLibrary" url="TestForm.xsn"/>
But if you just put the XSN files in a module and deploy it to a Form-library like this, or just upload the xsn file to the library, the Info Path form will not be able to render (error: form is not browser enabled).
What you have to do to fix this is adding some extra properties:  1<elements xmlns="">
 4       rootwebonly="FALSE"
 5       url="Lists/Forms">

Deploy Info path using PowerShell, SharePoint 2013

INTRODUCTION This post aims to describe how to deploy infopath forms as form templates in a sharepoint site using Powershell.
SCOPE This post will not detail out how to create a custom infopath form. It will assume that there is already an existing Infopath source files that are for deployment. REQUIREMENTS Sharepoint 2010 Microsoft Infopath Designer 2010
1.Locate the manifest.xml, right-click and click on Design. The Infopath Designer should load.

2.Whenever modifications have been made to the form, it is a good practice to change the version of the infopath form. This is because when you create a version 1.0 and so on for a form, all of the previous versions will be saved in Sharepoint. To do this, Click on File on the Infopath Form Designer. On the Info Ribbon tab, Click on Advanced Form Options. The Form Option dialog box should appear.

3.Change the version on the Version field. 4.[Not Required] If you would like to create another set of source files for the modified I…

Activate / Deactivate Feature with PowerShell on all site collections of the webapp


When we do some change on the solution  specially on the branding  for exmple ( display teamplate),we should update also existing sites collection and replace old files with new one after the deployment. So this powershell Script with do this on the all farm. $feature = Get-SPFeature -Identity "ID OF THE FEATURE" $siteCollections = Get-SPSite –WebApplication $webhubUrl -Limit ALL $siteCollections | foreach-object {    Write-Host "Deactivating" $feature.DisplayName "on" $_.Url -foregroundcolor yellow    Disable-SPFeature $feature -Url $_.Url -confirm:$false
} $siteCollections | foreach-object {    Write-Host "Activating" $feature.DisplayName "on" $_.Url -foregroundcolor green    Enable-SPFeature $feature -Url $_.Url