Once again I was compelled to swoop in to fix a managled set of Metadata and Content Types for a key document library. The simplest of the challenges was removing metadata from Folders, or so I thought. In this case, somehow, all the fields in the Document Library were associated with the Folder Content Type, so adding a new folder presented the user with roughly ten fields to complete; which were not needed.
First attempt was to hide the fields, which didn’t succeed:
$Fields=$tContentType.Fields; $Fields[$Field].set_showinaddform($false); $Fields[$Field].set_showineditform($false);
I then tried the old standby of trying to remove the field, where $i is the index of the field within the Content Type:
$Fields=$tContentType.Fields; $Fields.item($i).remove()
I then tried my usual approach to redo the FieldLinks that is the list of fields to present for forms, by removing the selected fields, to no avail:
$fieldLinks = $tContentType.FieldLinks; #simple shortcut reference $fieldList = New-Object 'System.Collections.Generic.List[System.String]' #new ordered list of fields # add everything to the list EXCEPT the fields to be removed for ($i = 1; $i -le $FieldLinks.Count; $i++) { $FieldName=$FieldLinks[$i - 1].Name; If ($FieldsToEliminate -notcontains $FieldName) #if this is a field that belongs {$fieldList.Add($FieldName); } $FieldLinks.Reorder($fieldList.ToArray()) #convert fields to array as we trigger Reorder method on fields $tContentType.Update() By this time, I was getting pretty hot under the collar, spending hours wrestling with removing a few fields from a Folder Content Type. This simple script did the trick. Here it is as a function. Note how I defined the parameter types, and also take care to clear and restore the ReadOnly flag, for any Content Type that started out Read-Only: Function Eliminate_Visible_Fields_ContentType( [Microsoft.SharePoint.SPContentType]$tContentType , [System.string]$tFields ) { $originallyReadonly = $tContentType.readonly; if ($originallyReadonly) {$tContentType.set_readonly($false)}; $FieldsToEliminate = $tFields.Split(“,”) #convert set of fields into array $Fields=$tContentType.Fields; foreach($field in $FieldsToEliminate) { $tContentType.FieldLinks.delete($field); } Write-Output([System.String] "Content Types stripped!") $tContentType.Update() if ($originallyReadonly) {$tContentType.set_readonly($true)}; } |
A few points to note:
- The input parameter tFields is a comma separated string of field names
- The field name expected is the “Internal” field name. That means the ugly name with the internal hex characters. So my field “Project Num” can be deleted only by referencing “Project_x0020_Num”.
- SharePoint Manager can be used to derive the intername field names
- Referencing the RootWeb Field list can get you the internal field names programmatically
- Trying to delete the public and internal names is safe. Best is to add them both to the list to be deleted; the correct one will be deleted.
Want to talk?
Drop us a line. We are here to answer your questions 24*7.