Tag Info

Hot answers tagged

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


2

The Modified By property is updated automatically by SharePoint each time a version is created with the current logged in user. Looking at the version history will show who edited the document and when.


2

Sharepoint 2007 and earlier are not (AFAIK) validate-able. Sharepoint 2010 and up are (AFAIK). However! This will require that your systems are Part 11 compliant. Being Part 11 compliant means not needing hard copies of everything for regulations. It's pretty costly to validate your system, since you have to take lots of measures to prevent false data being ...


2

Did they look in the recycle bin? Global versioning is a bad idea for a training issue, storage costs will skyrocket as Sharepoint doesn't do diff versioning, it's a copy of the item. I've seen single document libraries with a handful of files get into the gigabyte ranges because of versioning and improper setup. Imagine that farm wide with every file. ...


2

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


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


2

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


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

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

What you've been prompted when uploading the file is probably a custom text column for that purpose. You should check that column. Version history is differnet and built-in functionality and you don't get prompted for that but its initialy 0.1 and increases with every edit depending on library's versioning settings. I don't know an easy way to jump to ...


1

Try running the PSConfig.exe utility on each server, this should sort out the mismatch. http://technet.microsoft.com/en-us/library/cc263093(v=office.12).aspx


1

Add the version column to the current view and selected "Export to Excel".=) Or of course you can do that programmatically using SPFile.UIVersionLabel for example: using (SPSite site = new SPSite("Your site url")) { using (SPWeb web = site.OpenWeb()) { SPList docs = web.Lists["Your library name"]; foreach (SPFile file in ...


1

To your custom contribute level, add the permission "View Versions". This enables user of the group to view versions and edit items. They can't delete items nor versions, if you don't allow them to. More to read: Create custom permissions - for SharePoint


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

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