I came across these notes on creating custom list templates when I was searching for a quick reference on list types and base type definitions to use in the CAML ListTemplate element. I copied them verbatim here for my reference. The original post can be found here: http://karinebosch.wordpress.com/walkthroughs/create-custom-list-templates-in-caml/
Important details to note are:
- FeatureId (optional): This is the ID of the feature in which the list template is defined
- BaseType (required): Specifies the base type, or default schema, for lists created using this template. See the table below for the 5 possibilities.
- Type: this is the template type on which the new list template is based. Se the table below for all base types of standard SharePoint list templates.
- DisplayName: the display name of the list template.
More details can be found in André Vala’s post.
The following table lists the 5 base types:
| Base Type |
Description |
| 0 |
Generic List |
| 1 |
Document Library |
| 3 |
Discussion List |
| 4 |
Survey |
| 5 |
Issue List |
The following table lists all available list templates with their template type id and their corresponding feature id:
| Type of list |
TemplateId |
FeatureId |
| Generic List |
100 |
00BFEA71-DE22-43B2-A848-C05709900100 |
| Document Library |
101 |
00BFEA71-E717-4E80-AA17-D0C71B360101 |
| Survey |
102 |
00BFEA71-EB8A-40B1-80C7-506BE7590102 |
| Links List |
103 |
00BFEA71-2062-426C-90BF-714C59600103 |
| Announcements List |
104 |
00BFEA71-D1CE-42de-9C63-A44004CE0104 |
| Contacts List |
105 |
00BFEA71-7E6D-4186-9BA8-C047AC750105 |
| Events List |
106 |
00BFEA71-EC85-4903-972D-EBE475780106 |
| Tasks List |
107 |
00BFEA71-A83E-497E-9BA0-7A5C597D0107 |
| Discussion List |
108 |
00BFEA71-6A49-43FA-B535-D15C05500108 |
| Picture Library |
109 |
00BFEA71-52D4-45B3-B544-B1C71B620109 |
| Data Sources |
110 |
00BFEA71-F381-423D-B9D1-DA7A54C50110 |
| Site template gallery |
111 |
|
| User Information List |
112 |
|
| Web Part gallery |
113 |
|
| List Template gallery |
114 |
|
| XML Form Library |
115 |
00BFEA71-1E1D-4562-B56A-F05371BB0115 |
| Master Pages gallery |
116 |
|
| No-Code Workflows |
117 |
00BFEA71-F600-43F6-A895-40C0DE7B0117 |
| Custom Workflow Process |
118 |
00BFEA71-2D77-4A75-9FCA-76516689E21A |
| Wiki Page Library |
119 |
00BFEA71-C796-4402-9F2F-0EB9A6E71B18 |
| Grid List |
120 |
00BFEA71-3A1D-41D3-A0EE-651D11570120 |
| Data Connection Library |
130 |
00BFEA71-DBD7-4F72-B8CB-DA7AC0440130 |
| Workflow History |
140 |
00BFEA71-4EA5-48D4-A4AD-305CF7030140 |
| Gantt Task List |
150 |
00BFEA71-513D-4CA0-96C2-6A47775C0119 |
| Meeting Series List |
200 |
|
| Meeting Agenda List |
201 |
|
| Meeting Attendees List |
202 |
|
| Meeting Decision List |
204 |
|
| Meeting Objectives List |
207 |
|
| Meeting Things to Bring List |
211 |
|
| Meeting Workspace Pages List |
212 |
|
| Blog Posts List |
301 |
|
| Blog Comments List |
302 |
|
| Blog Categories List |
303 |
|
| Status Indicator (KPI) List |
432 |
7ED6CD55-B479-4EB7-A529-E99A24C10BD3 |
| Report Library |
433 |
6E53DD27-98F2-4AE5-85A0-E9A8EF4AA6DF |
| Publishing Pages Library |
850 |
|
| Issue Tracking List |
1100 |
00BFEA71-5932-4F9C-AD71-1557E5751100 |
| Administrator Tasks List |
1200 |
|
| Translation Management Library |
1300 |
29D85C25-170C-4df9-A641-12DB0B9D4130 |
| Translation List |
1301 |
29D85C25-170C-4df9-A641-12DB0B9D4130 |
| Slide Library |
2100 |
0BE49FE9-9BC9-409d-ABF9-702753BD878D
I recently had to integrate jCarousel into a SharePoint web part. Since jCarousel is a plugin for jQuery, it means I also had to get jQuery integrated with SharePoint. In order to accomplish this, I followed some good feature packaging instructions found from a few different blog posts:
After figuring out how to package jCarousel and jQuery using SharePoint delegate controls, I was ready for business with the implementation of the web part.
The web part itself was nothing fancy. I used a Repeater control to generate the list item (LI) elements with the content I needed in the carousel. I wrapped the Repeater in an unordered list (UL) which was wrapped in a DIV tag that had the runat attribute set to server. So basically, I just followed the mark up instructions provided in the jCarousel documentation.
The wrapping DIV tag was used in my webpart code to initialize jCarousel. The code snippet below shows how I implemented it:
protected override void OnLoad(EventArgs e)
{
if (!Page.ClientScript.IsStartupScriptRegistered(this.GetType(), this.ClientID))
{
Page.ClientScript.RegisterStartupScript(this.GetType(), this.ClientID, @"
<script type=""text/javascript"">
jQuery(document).ready(function() {
jQuery('#" + carouselDiv.ClientID + @"').jcarousel({
// Configuration goes here
vertical: true,
scroll: 2,
visible: 4
});
});
</script>
");
}
}
Service Pack 2 for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 have been officially annouced and are available for download from the Microsoft Download Center. I ran across the annoucement on the Microsoft SharePoint Team Blog where you can find links to the knowledgebase articles, downloads, and other resources including installation instructions. Below are quick links for the downloads:
SP2 for WSS 3.0: http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
SP2 for MOSS 2007: http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
[Via Joel Oleson]
I love finding a good and useful blog post and this morning I did just that. The post from Joel Oleson regading SharePoint test driven development is great. It has a quick exerpt from his twitter conversation with other SharePoint pros regarding this topic, a summary of what he learned, and list of useful resources with descriptions. If you follow or practice test driven development (TDD) and are involved with SharePoint development, then this post will be a good resource for you too.
SharePoint Designer (SPD) is a nifty tool to use to customize SharePoint sites. It is very powerful and allows us to quickly make style, organizational, functional, and content changes quickly and easily. Today, I ran across a post from Joel Oleseon where he shared his professional opinion in response to another post about the tool from Mark Rackley which was motivated in response to Microsoft’s announcement to make the tool available for free. There really is nothing new about the debate as it deals with the advantages and disadvantages of empowering an end user with all of the power the tool has to offer. It has just resurfaced since the tool will be freely available.
So… if the debate is not new, what’s all the fuss about?
Regardless of the stance that you take about allowing SPD to be used in a production SharePoint deployment or not, the real cause of concern is how SPD can impact production environment when used by untrained/uninformed users with appropriate rights. This reminds me of the quote – with great power comes great responsibility… or something like that. I don’t see the need for huge concern. That is assuming people with those rights have already been trained and informed. For the most part, people with contributor or higher permission role assignments can already do plenty of damage to a production environment with only the web browser at hand. Hence, the need and argument for appropriate training, content approval (and publishing) planning and enforcement, and governance plans (especially in Extranet/Internet facing deployments).
Okay… so what should we do?
There shouldn’t be too much to do (assuming training, content approval, governance, etc. has already been addressed). Professionally, I will be making sure to emphasize the role of SPD in SharePoint projects. I will also make sure to encourage the inclusion or addition of SPD training for existing and new SharePoint users (especially “power” users), administrators, and developers.