13

Actually, you don't need SharePoint Designer in order to achieve this. Instead you can use "Content and Structure" which is built into the SharePoint UI itself. "Content and Structure" is availabe on the Site Settings page after you have turned on the Site Collection scoped feature "SharePoint Server Publishing Infrastructure" (this is the name in ...


12

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


9

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


7

Both lists and libraries can use Versioning, the file type does not matter in the case of documents.


6

For future reference: there's a legacy API used by SharePoint Designer, called FrontPage RPC, and there's a bunch of methods, including move document that accepts a put_option parameter with migrationsemantics flag to preserve the information about who created a document, who modified it, and when it was created, and this could be used from advanced workflow ...


6

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.


6

Right click on version link [Ex: 14.11.2011 12:57] and open in new browser, pop up comes up with open/save option.Click on save button to save the specified version of the document.


6

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?


5

SharePoint doesn't support multiple versions of folders in Lists and Libraries.


5

There's a new solution in Office 365. You can now select a file or group of files in the modern experience in OneDrive or SharePoint and select Move to. A file or group of files moved this way will retain version history. This change is currently marked "Rolling Out" on the Office 365 Roadmap and their are more details about the roll-out schedule on the ...


5

Our method was uploading the infopath form to the destination libary and deselecting "Enable this form to be filled out by using a browser". This way the content types in the from library matched the content types in the to library.


5

Name the file you want to upload doc1.pdf. Go to "Upload" like you are adding a new file to the SharePoint folder. However, make sure the checkbox is selected "Add as a new version to existing files". This will overwrite the current doc1.pdf but keep your versioning.


5

I asume you are filtering by site and not by library. You could do something like this: $ignoreSites = @("http://siteurl/site1", "http://siteurl/site2") Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue $siteURL = $args[0] $site = Get-SPSite($siteURL) $webs = $site.AllWebs | ? {$_.Url -notin $ignoreSites} foreach($web in $webs) { ...


5

No, it's not possible to set the document version number manually in all SharePoint versions, As a workaround solution In case the current document version number in the test site is higher than document version number in the live site. Perform multiple check out and check in to reach the desired version number In case the current document version ...


5

If you read this question/answer you find a powershell script to have back the 'No versioning' option in libraries Site Assets library still carries the 'No versioning' option The final and draft status can be turned into a choice column that you switch at your need. However the concept of versioning is not the mere declaration that something is ...


4

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


4

//To move file from source library to destination through Event handler SPFile sourceFile = properties.ListItem.File; SPFile destFile = null; SPUser userCreatedBy = sourceFile.Author; DateTime dateCreatedOn = sourceFile.TimeCreated.ToLocalTime(); int countVersions = properties.ListItem.File.Versions.Count; for (int i = 0; i <= countVersions; i++) { ...


4

Not sure if this is the cause of your problem but... For documents, Before and After properties are guaranteed for post events, such as ItemUpdated, but Before properties are not available for post events on list items Reference:http://msdn.microsoft.com/en-us/library/ms463479.aspx If this is your scenario you may want to use properties.ListItem and ...


4

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


4

Yes, as per documentation: Simple versioning is available for site lists, but minor versions are not available. Each version of a list item is numbered with a whole number. If your organization requires approval of items in a list, the items remain in Pending status until they are approved by someone who has permissions to approve them. While in Pending ...


4

The content will be missing if you are adding this column to a document library or document set. Multi-line text fields act differently in Lists than in Libraries. If you don't get what you want here, you can create a custom list with a multi-line text field to hold the data and link it with a lookup field. Hope this helps, Mary Smith Greene


4

You can't use modified data as it will have the date for every metadata change. This may seem like an overkill for such a simple requirement, but I think you will need to write custom C# code using event receiver attached to list which will update a custom date/time column with the published date value if you want automation . Something as mentioned in below ...


4

I think you dont need to install the hotfix And MS14-202 due to fact that latest CU include all the previous fix.I would do the following way. Install the Service Pack 1 Mark 2.( as this is base line for future updates. Now install the June CU 2016( requirement for it is Service Pack 1). You can get more info from this official blog :June 2016 CU for ...


4

There's no global setting in SharePoint Online unfortunately. But its really not a big issue having 500 major versions on each document. Versioning just saves the delta (last changes) and not the entire document each time. IMHO you can safely ignore the setting and move on, since it won't effect performance, nor storage by much.


3

So while writing the question i answered my own question. "Draft Item Security" setting says "Only Users who can EDIT". So we must change to the permission-level from Full Read to Full Control, not the cleanest way to solve this, but it works. Have any input please let me know :)


3

I typically advise to place "shared" libraries into a dedicated WSP and keep it out project or function specific WSPs. If a specific WSP is retracted, the "shared" library will still be available. Examples of "shared" libraries are: log4net, Enterprise Library, your own shared libraries, ...


3

I haven't seen anything that will let you get that version information using the client api's. Since it is an on-prem server you could write some server side code to use the SPListItem.Versions functions to read the version info and return it to the client. I haven't checked but that function may be accessible from a sandbox solutions as well, if you can't ...


3

I don't see why you can't use the OOB versioning functionality. If you enable versioning and content approval for your library and turn on major and minor versions, then whenever a document is submitted, it is marked as Draft and it gets assigned a minor version. You can then use a standard approval workflow (or customize it to suit your needs) to approve ...


3

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


3

I've used code like this in a console app where I was reconfiguring some lists. This enables versioning and sets limits. var depts = web.Lists.TryGetList("Depts"); if (depts != null) { depts.EnableModeration = true; depts.EnableVersioning = true; ...


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