Tag Info

New answers tagged

1

It depends. If you have version control enabled - and you have saved at least once, then you can access that version from the version menu and restore it. If you are not using version control - then the answer is no, you can not "undo" the undo. The changes are unfortunately lost.


2

$web = Get-SPWeb -Identity http://sp2010 $list = $web.Lists["Documents"] $items = $list.Items foreach ($item in $items) { $file = $item.File $fileVersions = $file.Versions if ($fileVersions.Count -gt 0) { $fileVersions.Restore($fileVersions.Count - 1) } } UPDATE Please note that when any of ...


0

You should be able to recover it from Recycle bin. Versioning doesn't affect what gets into Recycle bin.


0

Using EventReceiver you can handle ItemUpdated public override void ItemUpdated(SPItemEventProperties properties) { base.ItemUpdating(properties); if(properties.ListItem.ModerationInformation==SPModerationStatusType.Approved) { //Remove permission } }


1

You should remove the previous content type before deploying the latest one. In some cases the removal will fail because its being using in the Site. The best practice in such situation is to use another feature with a receiver, the receiver is the one which make the updates (in your case adding a new site column) More details on this topic ...


0

I always employ the drag and drop method suggested by Tom. Easiest enough for my end users to do themselves and I still have the version history.


1

The SharePoint SQL Schema details are not documented. Its not documented because Microsoft don't want any one to touch it. There are complex job's etc running on these tables and a simple read operation can bring down the farm. SharePoint comes with various API to access the data.



Top 50 recent answers are included