Hot answers tagged

10

Providing you are using SharePoint 2010, you can move the files, with history, using the 'Open with Windows Explorer' functionality.


9

Sorry for localized version - it's a history list. Note marked link and url in status bar - it's archived version. So you can simply download. Edit Although when you hover over the Modified On value there is a dropdown list, the Save option isn't there. To save, right click on the Modifed On value and choose Save As. This will save the document version ...


7

Sorry to hear that but lists themselves are not versioned, they cannot be rolled back. You may want to consider database or site collection backup/restore. You may still lose some data depending upon the backup schedule.


6

Take a look at my answer provided to very similar question: Get meta data from a previous version of a document through webservice in MOSS 2007 Using web service and Lists.GetVersionCollection Method is (as far as I know) only available option. So you need to call it for each field of your item. Client object model is not an option. UPDATED To get all ...


6

Unfortunately list items do not support the same versioning hierarchy as documents, there are simply a number of versions against list items, which can be used for comparison purposes or for roll back.


5

Versions web service is no use in your case. You need to use Lists web service (http:///_vti_bin/lists.asmx) and Lists.GetVersionCollection Method Returns version information for the specified field in a SharePoint list. So you need to query field by field and as far as I know there is no method to return all field versions at once. Your code could ...


5

It is not supported to retrieve versions for a List Item via REST/CSOM APIs, but there are alternative options. Using Versions.aspx application page The idea is to perform a get request to Versions page : http://<server>/<site>/_layouts/versions.aspx?list={litsID}&ID=<itemID> and extract versions info from page content as ...


5

BUILT IN THINGS Version history is already in ribbon of a displayform.aspx. It is disabled by default. If you want to enable it, the go to list setting --> Versioning Settings and enable Create a version each time you edit an item in this list. CUSTOMIZATION Did not find any API for version history URL yet but you can construct it manually. There is ...


4

Consider using Chris O'Brien's Sharepoint Content Deployment Wizard: http://www.sharepointnutsandbolts.com/2007/12/introducing-sharepoint-content.html It can be found on CodePlex.


4

Frank, I don't think it's possible to do what you want. If search returned all of the versions, we'd have a real mess on our hands. You're right that the Author (Created By) is the original creator and the Editor (Modified By) is the last person who made an update. To add to the complexity, those roles may have only made changes to metadata and not the ...


3

The SharepointAudit logs keep track of that stoff if auditing is enabled on your site. You can use an SPAuditQuery to get all the Documents Frank van Puffelen updated. You could look at http://www.codeproject.com/Articles/431342/Auditing-A-Built-in-Feature-of-SharePoint


3

The "right" answer is in your point #2; don't do this as it is not supported. To address your point #1, any change made to files in /_layouts/ is farm wide so all lists everywhere will pick up the change immediately. If the client is really insisting on this then one option would be for you to copy the versions.aspx page to a custom folder under ...


3

The versioning in SharePoint is tracking Major (published with everyone, everything having 1.0, 2.0, etc.) and/or Minor (X.1, X.2, etc.). According to how you have setup Versioning via the List/Library Settings you would have Major or Major and Minor. In both cases when you limit versions, basically the OLDEST are deleted, so you would 0.1, 0.2, 0.3 as ...


3

You are looking for Auditing. But be careful, it can pretty fast get out of control and fill the servers hard drive and affect the performance. Make sure to trim the Audit logs to fit your requirements. Another god idea is to have SharePoint writing the log files to a separate drive. You can use the audit feature of Microsoft SharePoint Server 2013 to ...


3

One drawback that SharePoint lists have is that attachments are not versioned along with other changes to a list item when list versioning is enabled. If you want, you can create custom application for it.We need to attach receivers to the ItemAdding, ItemUpdating, ItemAttachmentAdding and ItemAttachmentDeleting methods. These will be used to push the ...


3

If you copy it using the Manage Content Tool from Site Actions doesn't that maintain the old copy and its history where it is? If you are only moving one or two files I wouldn't think you'd need more than that.


3

You could have a user control which display the BuildVersion of the farm, and show this within your MasterPage in the right place. The BuildVersion property: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spfarm.buildversion.aspx Creating User Controls for SharePoint: ...


3

If you take closer look at versions.aspx (\14\TEMPLATE\LAYOUTS) you will notice that 'nice summary' is created by iterating over item versions (from line 311 to 357). My guess is if versions.aspx uses iteration to retrieve field changes then this is the only option available. Edited: To be completely correct: It is not the only option. You can probably ...


3

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.


3

There are (at least) two ways to get the content of an old version of a file, both go through the SPFileVersion from item.File.Versions. If you want to use the content in your code, then you can call SPFileVersion.OpenBinary (or OpenBinaryStream) If you want to allow the user to download the content then you can provide a link based on SPFileVersion.Url ...


3

You can set Draft Item Security to Only users who can approve items (and the author of the item) in Versioning Settings of Document library. After the the user other than Other or Approver will be able to see the last pulished version only (i.e., 1.0,2.0,etc) Below is the screen shot after setting the option: Below is the screen shot with other user ...


3

Client Object Model doesn't have the property to retrieve the ListItem Version details. Instead SharePoint web service provide the option to retrieve the version details of a list item. We can use the below options to get the version details. SharePoint WebService to get Version Collection SPservices to retrieve version history of items from SharePoint ...


2

jus refer this link it may help u http://www.learningsharepoint.com/2010/09/05/programmatically-get-versions-for-files-in-sharepoint-2010-document-library/


2

It should be fine as long as you cut & paste (move) instead of copy & paste (copy).


2

There are two permissions regarding Versions View Versions Delete Versions If the user has only View Versions, then they cannot restore a previous version. However, if they have Delete Versions permission, then they can restore also. SO you may create a new Permission level and make sure that Delete Versions is unchecked. Then assign this permission ...


2

You can get the version history using following URL format /_layouts/Versions.aspx?list={list guid}&ID={item id} Replace List GUID and Item ID


2

Based on my testing and experience that is expected behavior of versioning and look up columns. As you can see in the Versioning Settings of the library, the Document Version History option is described as following: Create a version each time you edit a file in this document library? Now changing the value of the list item only affects the list ...


2

I'm guessing it is because of this section: "Modified By" = $item["Editor"] "Modified Date" = ($item["Modified"] -as [datetime]).DateTime In reality, you should be using $version to get to the version history of the item. You are iterating over each version of the item, yet you are referencing the item properties. Something like: "Modified By" = ...


2

As @John mentioned this can be done using code. You need to get SPListItemVersionCollection associated with the list item. Loop through the versions and keep track of current and previous version. Also, you need to check whether field needs to be shown in version history using SPield.ShowInVersionHistory I have created a custom solution which does version ...


2

The ribbon performs three checks before enabling the Version History button: Only one element has been selected The user has ViewVersions permissions to that item The List has versioning enabled You (or someone with access) can check these settings in powershell $w = Get-SPWeb SITE_URL $l = $w.Lists["Shared Documents"] $l.EnableVersioning Should show ...



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