Tag Info

Hot answers tagged

3

Use SPListItem.UpdateOverwriteVersion() Updates the item without creating another version of the item. SPListItem.SystemUpdate method More Explanation


3

I know this is not quite an answer you may be looking for, but why not rename doc2.pdf to doc1.pdf and then rename it in SharePoint itself?


3

$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 ...


2

The Content and Structure worked fine for me. Moving individual documents from one library to another captures all versions. Assuming, of course, versioning is configured the same on both libraries. That bit me the first time - the destination had Major, but the source had Major/Minor. Once the destination was switched to Major/Minor, documents came over ...


2

Sean It is possible to do this however you will need a workflow to run behind the scenes to create a sneaky URL with some specific elements in it to show the latest Published version of any document - i.e. the Major release. Basically the way SharePoint manages previous version of documents is in using a set of hidden folders of all the previous ...


1

You can't, this is an all or nothing setting. It is either content approval for everyone, or no one.


1

a. Create a new Permission Level copied from "Read" permission b. Remove "View Versions" option from the new permission level c. Set that new permission level to the users or groups Following are the steps... Go to the Site Collection > Top level Site > Site Settings > Site Permissions Click on "Permission Levels" from Ribbon > Permission Tools > Manage ...


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.


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 ...


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.


1

I found a solution here, it involves editing the Checkin.aspx page. This would affect every site collection in the farm, unless you wrap it in a feature. Open Windows Explorer to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS. Locate the file "checkin.aspx" and make a copy in case there is a problem. Open ...


1

When working with SharePoint remotely, you have to use CSOM and the CSOM model, you can't use any Microsoft.SharePoint.* objects. Everything is Microsoft.SharePoint.Client.*. Start here to get acquainted with CSOM: http://msdn.microsoft.com/en-us/library/ff798388.aspx


1

Read permission grants a user "View Version" base permission by default. If you have minor & major version turned on in a library, you can limit who can view the minor versions in the version history (readers, contributors, approvers) in List -> Settings -> Version Settings -> Draft Item Security.


1

Read permissions allow users to view past version history of list items. You can look at your permissions levels by going to Site Actions->Site Settings->Site Permissions, then click on Permissions Levels in the ribbon. I would suggest getting familiar with these permissions and perhaps creating your own to do what you want. Even Read permissions might ...


1

So now I feel really stupid. I went and look at the workflow and saw that I could select "Start this workflow to approve publishing a major version of an item." and of course that works perfectly.


1

I can verify that when using copy tool TeraCopy for uploading document via webdav (http://codesector.com/teracopy) version number of document gets set back to initial value and version history is lost.


1

Using some CAML tools pointed at a local library with versioning enabled, I was able to get back the field ows__UIVersionString of a file. It correctly shows the version is 9.0 which is reflected in the UI. <Where> <Eq> <FieldRef Name='ID' /> <Value Type='Counter'>1</Value> </Eq> ...


1

Next time you make changes to your CSS file, create your own rev/version tag where the CSS file is being referenced (probably your Master Page). This way the browser will break the cached CSS and re-retrieve thinking it's a new file. ex. <link href="/styles/style.css?rev=03_27_2014_v1" type="text/css" rel="stylesheet" />


1

For Checking-In it can be possible if you Enable Moderation and Enable Versioning in your list/library.. So once people Check-In the item, the changes will be visible to all approvers and once they review the changes (they can see Check-In comments in Version History), they can Publish the item to make the changes available to all users.. Now a problem with ...


1

I know it's been 3 years ago and already answered, but here you can find plenty of versioning scripts and ready programs: Disable a versioning on Image Libraries in SharePoint using PowerShell Enable versioning for all SharePoint Online lists using Powershell Enable versioning for all lists in SharePoint Online tenant (C#) Restore and clean up SharePoint ...


1

Here is the answer for Excel. A similar solution should work for Visio. Create a new column in your library called "SPVersion". Use SharePoint Designer to create a workflow that copies the file version ("Current Item" "Version") to your SPVersion column. In Excel, add the following VBA code to the ThisWorkbook module: Private Sub ...



Only top voted, non community-wiki answers of a minimum length are eligible