I wanted to purge the contents of a huge document library. Because of the 5000 item limit, using the GUI or explorer view wasn’t posssible any more. There are a couple of scripts out there which can help, based on the ProcessBatchData method to process batches of operations at once. This is often the best scenario, because deleting items one by one takes a lot of time.
Now upon deletion, you can get all kinds of non descriptive errors (operation failed, 0xblabla…). When your script fails after some items were deleted, there is a good chance check-outs are in the way of deletions. Checked-out files have to be checked-in again before they can be deleted, and folders to be deleted cannot contain any checked-out items either. So I create a purge script which takes care of all of these kinds of things, before deleting the entire contents of a library. I’m saving it here mainly for my own reference, but feel free to use it when you want to!
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 |
Add-PSSnapIn Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue # Appends a line to the deletion builder and outputs a line every # 100 items to track progress function AppendLine($line) { $deleteBldr.Append($line) > $null # global variable declared in PurgeDocumentLibrary Set-Variable -Name lines -Value ($lines + 1) -Scope Global # Write a line every 100 items to track the progress on this library if ($lines % 100 -eq 0) { Write-Host "Appended line $lines of $itemcount" } } # Helper function which processes an item. This way it doesn't matter # what type you put in, the correct function is always executed, or # an error is thrown when the type is unusable function ProcessItem($item) { if ($item -eq $null) { break } if ($item -is [Microsoft.SharePoint.SPFolder]) { ProcessFolder($item) } elseif ($item.FileSystemObjectType -eq "Folder") { ProcessFolder($item.Folder) } elseif ($item -is [Microsoft.SharePoint.SPFile]) { ProcessFile($item) } elseif ($item.FileSystemObjectType -eq "File") { ProcessFile($item.File) } else { throw "Woops, the $item of type $($item.GetType()) cannot be processed" } } # Processes a file; check-in when required and then append to delete function ProcessFile($file) { # When there is no item linked to this file, its a system file; break and ignore if ($file.Item -eq $null) { break } # When the file is checked out in some way; forcibly check it in if ($file.CheckOutType -ne "None") { $file.CheckIn("Automatic checkin") $file.Update() } $line = [System.String]::Format($command, $file.Item.ID.ToString(), $file.ServerRelativeUrl) AppendLine $line } # Processes a folder; first all subfolders and files in the folder and then # the folder itself. Appends a line for bulk deletion function ProcessFolder($folder) { foreach ($item in $folder.SubFolders) { ProcessItem($item) } foreach ($item in $folder.Files) { ProcessItem($item) } # only delete a folder when it has an item linked to it... folders without an item are system folders if ($folder.item -ne $null) { $line = [System.String]::Format($command, $folder.Item.ID.ToString(), $folder.ServerRelativeUrl) AppendLine $line } } # Processes a document library and purges all of its content. This includes check-in of files # without a checked-in version, or plain checked-out files (which cannot be deleted) function PurgeDocumentLibrary( [Microsoft.SharePoint.SPWeb] $spweb, [Microsoft.SharePoint.SPList] $splist) { Write-Host "Processing library $($splist.Title) with $($splist.ItemCount) items" # Create the batch string builder containing the command XML [System.Text.StringBuilder] $deleteBldr = New-Object "System.Text.StringBuilder"; $deleteBldr.Append("<?xml version=""1.0"" encoding=""UTF-8""?><Batch>"); $command = "<Method><SetList Scope=""Request"">" + $splist.ID + "</SetList><SetVar Name=""ID"">{0}</SetVar><SetVar Name=""owsfileref"">{1}</SetVar><SetVar Name=""Cmd"">Delete</SetVar></Method>"; # variable used in output to screen, to track progress $itemcount = $splist.FolderCount + $splist.ItemCount # forcibly check in any files which do not have a checked-in version... # otherwise these will cause errors foreach ($checkedOutFile in $splist.CheckedOutFiles) { $checkedOutFile.TakeOverCheckOut(); $listItem = $splist.GetItemById($checkedOutFile.ListItemId); $listItem.File.CheckIn("Automated checkin"); } # Process the root folder which will then recursively process all sub items, ProcessItem $list.RootFolder # append closing tag for proper XML structure $deleteBldr.Append("</Batch>") # Process the batch command and update the web (not strictly necessary) $command = $deleteBldr.ToString() $spweb.ProcessBatchData($command) $spweb.Update() } # start assignment for disposal Start-SPAssignment –Global Set-Variable -Name lines -Value 0 -Scope "global" # Get the web object, retrieve the list and call the Purge method $web = Get-SPWeb "http://www.contoso.com/subsite" $list = $web.Lists["Shared Documents"] PurgeDocumentLibrary $web $list # stop assignment for disposal Stop-SPAssignment -Global |
I want to delete all documents larger than 2 MB from SharePoint. How would I script that?
regards,
Praveen
Hi Praveen,
Using CSOM you can query the “File_x0020_Size” property to get the size of the file. You can use that in a CamlQuery to retrieve only those files larger than 2MB and you could use parts of the script above to delete them. See http://stackoverflow.com/questions/19292422/get-file-size-using-csom-in-sharepoint-2010 for more information on the file size property.