Search Results

Before you add a custom content type, you usually create site columns that meet your needs. See http://SiteCollectionURL/_layouts/15/mngfield.aspx where you add custom site columns.

Running Powershell and accessing a Subsite (and not the root web) you have to make a slightly different approach. You need to access the root web content type, and add that one to the subsite document …

Sealed Optional Boolean. TRUE to prevent changes to this content type. You cannot change the value of this attribute through the user interface, but you can change it in code if you have sufficient r …

Permission inheritance, and the breaking of inheritance, is in the realm of user access. A user authenticates herself to the environment, usually Active Directory, which verifies that the user is auth …

Didn't get Amals script to work, but used this instead. The real difference is $ct = $web.AvailableContentTypes. # Find all content types that use that column type # This will display all content t …

To share Content Types between Site Collections, you usually implement a Content Type Hub. The CT Hub publishes Content Types, which other Site Collections can subscribe to. That way the get the same …

Have you tried something like this? $snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'} if ($snapin -eq $null) { Write-Host "Loading SharePoint Powershell …

As it turns out, these "content types" comes from Office Online Server (formerly knows as, Office WebApps Server). The only way to change them is by adding custom content types. That goes from reorder …

When creating a new document library and selecting Document Template “None” or “Microsoft Word Document” (which is default), you get a list of office document template to choose from when you create a …

Create your own Content Type (MyFolder) which inherits from folder. Add your newly created MyFolder to your library, and you're good to go.

When you inherit Content Types, you should inherit as is. Otherwise you'll lose functionality of the default content type and breaks internal dependencies. That's the whole point of inheritance. Eithe …

Yes, through PowerShell. Phil Childs posted the article Export and import/create site columns in SharePoint using PowerShell back in 2011. Basically you export your site columns to an XML-file in you …

Instead of using $CT = $item.ContentType try using $CT = $item["ContentType"]

Typically you would create a template for the use when creating site. You don't have to create a new Document Library, simply add the Content Type with metadata, and remove the default "document" CT. …