Tag Info

Hot answers tagged

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

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

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

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

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

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

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

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

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

The page showing versions is accessible as <siteCollectionURL>/_layouts/versions.aspx?list=<ListID>&ID=<ItemId>&FileName=<ServerRelativeFileUrl> So you need to know ListID, ItemID and ServerRelativeFileUrl as parameters. ) To launch it via the Javascript you would need something along these lines ...


1

In addition to the code, the List/Document Library needs to have enabled the versioning setting(s) as well. In the SharePoint ribbon, in the Library tab, select the Library Settings button in the Settings area. In the settings page, under the General Settings header, you'll see Versioning settings. Here, you can select settings for versioning, and if you ...


1

You cannot, but since you already have your item in hand you can update your current row with latest item data. Something like: foreach (DataColumn column in results.Columns) { SPField field = newestItem.Fields.TryGetFieldByStaticName(column.ColumnName); if (field != null) { row[field.InternalName] = newestItem[field.InternalName]; } ...


1

Out of the box, this isn't possible. As I see it, no one has made one and it would require some really robust custom coding to utilise this: http://msdn.microsoft.com/en-us/library/microsoft.office.interop.word._document.trackrevisions So, the basics of creating one exist, but the actual thing so far doesn't seem to.


1

Sorry if I misunderstood the problem, it's seems like you're talking about the differences between author names of the document right ? My idea may be too easy but it may help to deep further. In SP, the "modified by" name is directly linked to the SP account, but in office document, there's also a native property named "Author", and other properties that ...


1

It depends on which technique you plan to use: Event Handlers - use ItemUpdating having properties object contains the collections BeforeProperties and AfterProperties that helps you to find out what has changed for your item, i.e. compare properties.BeforeProperties[].ToString() with properties.AfterProperties[].ToString(). You can also modify the value ...


1

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


1

If dazzles me a little, it seems you did enable Approval however you get still the version 1.0. Are you sure that versioning is enabled? If you only enable Major, then every Check In and Approve will move to 1.0, 2.0, etc. if you enabled Minor (that is Drafts) then Deepu's explanation is absolutely valid Check-In - Minor would increase/overwrite Minor ...


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

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


1

If you have versioning enabled on the list you can access the versions of a SPListItem by the SPListItem.Versions property. You could also use event receivers (SPItemEventReceiver) to track the changes and store the changes in another list.


1

After when you make the 2 fields from your InfoPath available as columns for SharePoint, you still need to create 2 calculated columns inside your SharePoint form library for each of the columns that you promoted to the library as column. Suppose one of the available column is called 'status', then in your Sharepoint form library, create a calculated column ...


1

1 user can not see the document history, nothing happens when clicking the link I guess that this is a client problem rather than a user account/ permission error. Can you check if the user is able to do all these things on another machine? If I understand correctly there is no "Acccess denied" message -right? So that might be client / browser / ...



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