Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Unable to customize version history

  Asked By: Dario    Date: Sep 26    Category: Sharepoint    Views: 4565

I want to create a new column in the version
history which is a list...

has any one gotta clue?



5 Answers Found

Answer #1    Answered By: Marty Mcdowell     Answered On: Sep 26

If your question is, "How do I add a column  to an Issues list  (the only
list that has version  history)"?

It is the same as adding a column to any other type of list. So, I'm
confused as to what your actual question is.

Answer #2    Answered By: Dakota Shaffer     Answered On: Sep 26

Hi has anyone gotta clue as how to add a new column  in
the issue history...which is a list??
i am stuck on that..........
There are default columns(Title; Assigned To;
Modified By; Comment; Modified)...but i want to add
a nw one...how to go about?

Answer #3    Answered By: Ted Gilmore     Answered On: Sep 26

Navigate to Documents and Lists

Click the Issue List in Question

Click Edit in Datasheet (which will switch to an Excel Style view)

Right Click on the First Highlighted row and click add Column,

You then set the parameters you require for you new column  etc

Answer #4    Answered By: Monte Cooley     Answered On: Sep 26

The alternative is one the Issue List click the "Modify Settings and Columns" and click "Add a new column"

Answer #5    Answered By: Guadalupe Bullock     Answered On: Sep 26

I think I finally understand your question. I will try and explain how you can add the Priority column  and remove the Assigned To column in the history  section at the bottom of the DispForm.aspx page of the Issues list. In the Before image below I identify the changes I think that you want to make.


To change this Web Part you will need to alter the SCHEMA.XML file associated with the Issues list. You should only do this on a Site Definition that you have created rather than on the existing built-in STS or MPS Site Definitions (or Portal Areas, etc.). See Creating a Site Definition from an Existing Site Definition in the SDK (I've also pasted it below). Also, this will only apply to sites that are created after you make your changes. It does not retroactively apply to existing Issues lists in existing sites.

1. Open the SCHEMA.XML from the 60 hive in Notepad (or FrontPage or VS.NET, etc.): C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\[YourSiteDefinition]\LISTS\ISSUE\SCHEMA.XML

2. Search for the View tag associated with the Issue History Web Part:
<View BaseViewID="5" Type="HTML">

3. Remove the following FieldRef tag from the ViewFields node:
<FieldRef Name="Assigned To"></FieldRef>

4. Add the following FieldRef to the ViewFields node:
<FieldRef Name="Priority"></FieldRef>

5. The resulting ViewFields node should look like this:
<FieldRef Name="LinkTitleNoMenu"></FieldRef>
<FieldRef Name="Editor"></FieldRef>
<FieldRef Name="Comment"></FieldRef>
<FieldRef Name="Modified"></FieldRef>
<FieldRef Name="Priority"></FieldRef>

6. Save the XML file and exit the editor.

7. run iisreset

8. create  and templatize a new site.

9. Create a new Issues list.

10. Add a list  item and then alter it so that there is a history to look at.

11. Finally, view the list item. It should look something like the After image below.


Remember, only Issues lists that are created on your new site will display the altered columns. New and existing lists on existing sites will continue to show the old set of fields.

From the SDK: Creating a Site Definition from an Existing Site Definition
You can create a site definition by copying and modifying an existing site definition. This task involves use of Collaborative Application Markup Language (CAML) in two schema files: one that is a copy of a WEBTEMP.XML file, and the other a copy of an ONET.XML file. It is recommended that you create a site definition as described in this topic rather than modifying the originally installed WEBTEMP.XML file.

Copy the existing site definition folder located in the Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\1033 directory.
For example, to create a custom site definition that derives from the site definition for Microsoft Windows SharePoint Services, copy the STS folder located in the 1033 directory. Name the new folder using all capital letters.

Make a copy of the WEBTEMP.XML file located at Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\1033\XML.
Give the file a unique name by appending a string to the name of the original file; for example, WEBTEMPACTION.XML. At run time, the compiler merges information contained in this file with the information contained in the original file in order to specify which site templates are available for creating new sites.

Customize the contents of the new WEBTEMP file.
Each WEBTEMP.XML file contains a collection of Template elements and Configuration subelements, which identify to the compiler all the site definitions that can be instantiated. The Configuration element defines a title, a description, and a URL for the image displayed in the user interface, properties common to each Web site created using the site definition.

Important In each Template element defined in the WEBTEMP file, the Name attribute must contain the same name, in all capital letters, that is assigned to the new folder. Also, in order to avoid conflict with IDs already used in Windows SharePoint Services, use unique values greater than 10,000 for the ID attribute.

The following example defines a single site definition. The example assumes the existence of an ACTIONCOMMITTEE directory that has been created as previously described.

<?xml version="1.0" encoding="utf-8" ?>
<Templates xmlns:ows="Microsoft SharePoint">
<Template Name="ACTIONCOMMITTEE" ID="10098">
<Configuration ID="0" Title="Action Committee Team Site" Type="0" Hidden="FALSE" ImageUrl="images/stsprev.jpg" Description="This template provides a forum for the team to create, organize, and share information quickly and easily. It includes a Document Library, and basic lists such as Announcements, Events, Contacts, and Quick Links."> </Configuration>
Save the file.
You may need to reset Internet Information Services (IIS) for the new template to appear as an option on the Template Selection page.

Didn't find what you were looking for? Find more on Unable to customize version history Or get search suggestion and latest updates.