Tag Info

Hot answers tagged

3

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


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


2

You can view the item history for a file and delete all previous major and minor versions. To do it in bulk, I found this post describing how to do it with PowerShell: [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") # get site $site = new-object Microsoft.SharePoint.SPSite("http://mossdev:8000") # loop through webs foreach ...


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

While creating the target label you can let SharePoint know how you want existing pages to be updated, when the changes are being done to the actual source page Users can manually sync updates from source variation pages will let end-users to choose which one to accept. Automatically update target variation pages will automatically update the target ...


2

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


2

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


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

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

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

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

Since the Published and Draft documents have the format: {MajorVersionNumber}.0 for Published {MajorVersionNumber}.{MinorVersionNumber} for Drafts for your scenario the View could be created with the following filters: By Published documents that corresponds to [Version] CONTAINS .0 By Author [Created By] = [Me]


1

So me and a friend (Mattias Ã…hlin) at work solved the issue. To get the functionality as with before and after properties and if() statments with the same result as the code does down bellow. So to answer my question, one of the problems with Before and After properties with versioning is that it's not 100% complete. In some cases the before value (of ...


1

The only property of a folder that you can change in the UI is the title. Changing this property doesn't update the version, and, the Version History button is greyed out for folders. So SP certainly doesn't track versions of folders out of the box, I don't know if it's possible to do something with an event receiver in code to forcibly update it or not. ...


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

I used managed CSOM to complete the same task before. You can find the code at http://wp.me/p23FqP-1U. I am not good at JavaScript. Hopefully you can work out the JavaScript from my C# code. Here is my C# code public void CopySharePointDocument(string siteUrl, string srcUrl, string desinationUrl) { var relativeSrcUrl = ...


1

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


1

The best (and easiest) way that I've found to remove that notice was a workaround posted on this Consulting blog. Using SPD, you are basically going to export a copy of the site to your local machine, re-upload it, and behold: the blue info icon is gone (which denotes that the site has deviated from the template). You can then delete the problematic page, ...



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