Tag Info

Hot answers tagged

9

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


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.


7

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


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

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


4

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


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

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

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.


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

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

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


2

One approach would be to use a content migration tool such as Metavis http://www.metavistech.com/ which enables you to move/copy files and lists while keeping version histories.


2

Yeah, you can't really do that, as far as I know (and yes, this is fine in other EDRMSs) What I'd suggest is something like having 2 libraries - .doc and .pdf - and create lookup columns to refer between them. I recognise that this means having 2 version histories - and that's not great - but SharePoint doesn't seem to deal with file type changes well.


2

Not sure this will solve your problem completely, but may help a bit. To see the SQL being executed, you could enable and use the developer dashboard.


2

You can also try the free edition of CopyMove for SharePoint 2007. It maintains the full version history and Metadata on documents that you copy or move.


2

To make things even simpler on yourself, I would recommend using SPServices. It has full support for the Versions web service in both SharePoint 2007 and 2010, which enables you to call the GetVersions method exposed by that service. For example: $().SPServices({ operation: "GetVersions", fileName: "http://spsrv2010/DocLib/file.txt", ...


2

What you need is to Restore the 10.0 as the current welcome page and then it will become 10.3 and you'll be able to Delete both 10.1 and 10.2


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


2

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


2

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


2

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


2

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


2

If you open the document with Word, then you are not likely opening the document with the credentials used by Firefox. If word is not prompting you to enter credentials when opening the file, then it is most likely using your windows credentials. In order to properly test this sort of thing, I generally try to logon to windows as the user I want to test.


1

If the task is to insert the version history of the word document into the document when generating and sending the pdf then you can use Open XML SDK to generate a temporary document with the version history and then Word Automation service to generate the pdf. A good starting point is the MSDN article Developing with SharePoint 2010 Word Automation ...


1

could you try this piece of code?The below code retrieves the content of the wikipage(published) foreach (SPListItemVersion objVersion in objVerisionColl) { if (objVersion.ListItem.Versions.GetVersionFromLabel(objVersion.VersionLabel).IsCurrentVersion) { bool ...


1

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/


1

look here, you must use SPFile not SPListItem: foreach (SPFile file in folder.Files).......... if (file.CheckOutType != SPFile.SPCheckOutType.None) { html.Append(" Estratto da<a href='" + mySiteHostUrl + file.CheckedOutByUser.LoginName + @"' class='author'>" + file.CheckedOutByUser.Name + @"</a>"); } ...


1

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.


1

I decided I didn't need to have both the EOD Status and EOD Status History fields showing up in version history, so I used SharePoint Manager to prohibit the history field from being displayed there. Working theory (as in, unverified but makes sense) to explain the behavior is since the field is not on the new or edit form, the existing value is not ...



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