Quick Reference for SharePoint Built in Fields

By -
There are many instances where you need a quick, readable reference giving you the GUIDs for your FieldRef's in a content type definition file. Here's a handy xslt stylesheet that does the transform for you:

<?xml version="1.0" encoding="utf-8" ?>

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:wss="http://schemas.microsoft.com/sharepoint/">

<xsl:output method="html" version="1.0" encoding="utf-8" indent="yes" />

<xsl:template match="wss:Elements">
 <html>
  <body>
   <h2>SharePoint 2007 Built-In Fields</h2>
   <table border="1" width="100%" style="font-size:10pt;">

    <tr bgcolor="#9acd32">
     <th align="left">Group</th>
     <th align="left" width="100">Field</th>

     <th align="left">Type</th>
     <th align="left">Declaration</th>
    </tr>
    <xsl:apply-templates>

     <xsl:sort select="@Group" />
     <xsl:sort select="@Name" />
    </xsl:apply-templates>
   </table>

  </body>
 </html>
</xsl:template>
<xsl:template match="wss:Field">
 <tr>
  <td width="100"><xsl:value-of select="@Group"/></td>

  <td width="100"><xsl:value-of select="@Name"/></td>
  <td width="100"><xsl:value-of select="@Type"/></td>
  <td>&lt;FieldRef ID=&quot;<xsl:value-of select="@ID"/>&quot; Name=&quot;<xsl:value-of select="@Name"/>&quot;/&gt;
  </td>

 </tr>
</xsl:template>
</xsl:stylesheet>



If you want everything done for you, save the above text into a file called "GenerateFieldDefs.xsl" and then save the below code into a document called "GenerateFieldDefs.html" and save both files into your SharePoint fields directory (..../12/TEMPLATE/FEATURES/fields). Then open the GenereateFieldDefs.html file with IE6 or Firefox 1.5 or higher.

Here's the html code:

<html>

<head>
<script>
function loadXMLDoc(fname)
{
var xmlDoc;
// code for IE
if (window.ActiveXObject)
{
xmlDoc=new ActiveXObject("Microsoft.XMLDOM");
}
// code for Mozilla, Firefox, Opera, etc.
else if (document.implementation
&& document.implementation.createDocument)
{
xmlDoc=document.implementation.createDocument("","",null);
}
else
{
alert('Your browser cannot handle this script');
}
xmlDoc.async=false;
xmlDoc.load(fname);
return(xmlDoc);
}

function displayResult()
{
xml=loadXMLDoc("fieldswss.xml");
xsl=loadXMLDoc("GenerateFieldDefs.xsl");
// code for IE
if (window.ActiveXObject)
{
ex=xml.transformNode(xsl);
document.getElementById("example").innerHTML=ex;
}
// code for Mozilla, Firefox, Opera, etc.
else if (document.implementation

&& document.implementation.createDocument)
{
xsltProcessor=new XSLTProcessor();
xsltProcessor.importStylesheet(xsl);
resultDocument = xsltProcessor.transformToFragment(xml,document);
document.getElementById("example").appendChild(resultDocument);
}
}
</script>
</head>
<body id="example" onLoad="displayResult()">
</body>
</html>


Comments

Post a Comment

Popular posts from this blog

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD...
Read more

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just...
Read more