Error while saving list as list template

If we try to save a large list as a list template, we may see the following error due to the list being too large:

"The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes."

We can increase the maximum size of a list / site template by running the following command
stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 50000000

Some imp points about this command:

• The propertyvalue parameter is in bytes, so the example above will increase the maximum size to approx 50MB.
• There is a hard limit of 500MB so the value must be less than 524288000 or you will get an error when saving the list as a template.
• The above increases the maximum size of both site and list templates

See Also: SharePoint Object Model Code to Create a SharePoint List using List Template: Code for Creating List using List Template

Attempt A Question On List Backup: Question on List Backup

Attempt A Question on Site Template: Question On Site Template

Take a multiple question test on SharePoint

If you want to take a beginner level test on SharePoint go to:
SharePoint Test Link
This test contain 20 multiple type questions on SharePoint.

Playing Audio/Video files within SharePoint Application

To play the Audio/Video files in SharePoint follow these steps:

1. Upload the file into a document library.
2. Add a content Editor Web Part to your site.
3. Add the code in the HTML:

<OBJECT id="VIDEO" CLASSID="CLSID:6BF52A52-394A-11d3-B153-00C04F79FAA6" type="application/x-oleobject">
<PARAM NAME="URL" VALUE="fileurl">
<PARAM NAME="SendPlayStateChangeEvents" VALUE="True">
<PARAM NAME="AutoStart" VALUE="True">
<PARAM name="uiMode" value="none">
<PARAM name="PlayCount" value="1">
</OBJECT>

Notes:
1. CLASSID="CLSID:6BF52A52-394A-11d3-B153-00C04F79FAA6" is the class id for Windows Media player.
2. URL will point to the location of the file. Upload this file to document library and put the URL for that file.
3. autoStart specifies value indicating whether the current media item begins playing automatically.
4. uiMode specifies which controls are shown in the user interface.
Possible values: invisible, none, mini, full.
5. PlayCount specifies the number of times a media item will play. Minimum value of one.

Get the code here:

You may find interesting to read: Showing PDF documnet in SharePoint Pages

Attempt a question on Web Parts: Question on Web Parts

Introduction to Social Networking Web Parts in SharePoint 2007

Colleagues Web Part: This web part helps users to present their colleagues to visitors. The colleagues list is a presentation of other organization members that the specified user works closely with in terms of organizational structure, interaction (that is, e-mail and instant messaging conversations) and memberships. Users can also manually add and remove colleagues.

Colleague Tracker Web Part: This web part enables organization members to privately view their list of compiled colleagues and to modify their views and inclusion in their colleagues list. The colleague tracker Web Part enables the presentation of recommended colleagues and enables the user to modify colleague tracking by profile information. For example, users can modify the colleague tracker to present updated colleagues when anniversaries, profile properties, authored documents, and blogs change. Additionally, scoping the presentation can occur when users choose to view colleagues specifically for the user’s workgroup or organization-wide.

SharePoint Sites, Links, and Membership Web Parts: Provide the ability for users to view their own Office SharePoint Server site, group and mail list memberships and links as well as those that they have in common with others. Additionally, visitors can view a user’s memberships, Office SharePoint Server Sites and distribution group memberships.

In Common With Web Part: Provides a summary view of information relating to the memberships, organizational managers and colleagues that a visitor has in common with the owner of a My Site.

Presence Information: When coupled with Office Communications Server and Exchange Server, presence information that indicates online instant messaging status, Out of Office messages and contact information is displayed whenever user information is presented (that is, colleagues and colleague tracker Web Parts, etc.).

Some Important Tables with SharePoint 2007

Here is the list of some important tables in SharePoint Content DB:

• Sites: This Table holds information about all the site collections for this content database.
• Webs: This Table holds information about all the specific sites (webs) in each site collection.
• UserInfo: This Table holds information about all the users for each site collection.
• Groups: This Table holds information about all the SharePoint groups in each site collection.
• Roles: This Table holds information about all the SharePoint roles (permission levels) for each site.
• AllLists: This Table holds information about lists for each site.
• GroupMembership: This Table holds information about all the SharePoint group members.
• AllUserData: This Table holds information about all the list items for each list.
• AllDocs: This Table holds information about all the documents (and all list items) for each document library and list.
• AllUserData: This table has all the metadata which user provides in a document library.
• RoleAssignment: This Table holds information about all the users or SharePoint groups that are assigned to roles.
• SchedSubscriptions: This Table holds information about all the scheduled subscriptions (alerts) for each user.
• ImmedSubscriptions: This Table holds information about all the immediate subscriptions (alerts) for each user.

Some queries with these tables:

-- Query to get all the top level site collections

SELECT SiteId AS Siteid, Id AS Webid, FullUrl AS FURL, Title, Author, TimeCreated FROM dbo.Webs WHERE (ParentWebId IS NULL)

-- Query to get all the child sites in a site collection

SELECT SiteId AS Siteid, Id AS Webid, FullUrl AS FURl, Title, Author, TimeCreated FROM dbo.Webs WHERE (NOT (ParentWebId IS NULL))

-- Query to get all the SharePoint groups in a site collection

SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.Groups.ID AS Expr1, dbo.Groups.Title AS Expr2, dbo.Groups.Description FROM dbo.Groups INNER JOIN dbo.Webs ON dbo.Groups.SiteId = dbo.Webs.SiteId

-- Query to get all the users in a site collection

SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.UserInfo.tp_ID, dbo.UserInfo.tp_DomainGroup, dbo.UserInfo.tp_SiteAdmin, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Email FROM dbo.UserInfo INNER JOIN dbo.Webs ON dbo.UserInfo.tp_SiteID = dbo.Webs.SiteId

-- Query to get all the members of the SharePoint Groups

SELECT dbo.Groups.ID, dbo.Groups.Title, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login FROM dbo.GroupMembership INNER JOIN dbo.Groups ON dbo.GroupMembership.SiteId = dbo.Groups.SiteId INNER JOINdbo.UserInfo ON dbo.GroupMembership.MemberId = dbo.UserInfo.tp_ID

-- Query to get all the sites where a specific feature is activated

SELECT dbo.Webs.Id AS WebGuid, dbo.Webs.Title AS WebTitle, dbo.Webs.FullUrl AS WebUrl, dbo.Features.FeatureId, dbo.Features.TimeActivatedFROM dbo.Features INNER JOIN dbo.Webs ON dbo.Features.SiteId = dbo.Webs.SiteId AND dbo.Features.WebId = dbo.Webs.Id WHERE (dbo.Features.FeatureId = '00AFDA71-D2CE-42fg-9C63-A44004CE0104')

-- Query to get all the users assigned to roles

SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login FROM dbo.RoleAssignment INNER JOIN dbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOIN dbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOIN dbo.UserInfo ON dbo.RoleAssignment.PrincipalId = dbo.UserInfo.tp_ID

-- Query to get all the SharePoint groups assigned to roles

SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.Groups.Title AS GroupName FROM dbo.RoleAssignment INNER JOINdbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOIN dbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOIN dbo.Groups ON dbo.RoleAssignment.SiteId = dbo.Groups.SiteId AND dbo.RoleAssignment.PrincipalId = dbo.Groups.ID

You can also find interesting to read Different Database created with SharePoint

SharePoint Terminology

Here are some important terms pertinent to SharePoint Technology:

• Application page: Allows the use of inline custom code. Application pages or "_layout" pages are stored on the SharePoint Web server and made available via a Microsoft Internet Information Services (IIS) virtual directory. Though application pages behave much like other ASPX pages and allow the use of inline custom code, they differ from content pages in that they cannot be used to host SharePoint features such as dynamic Web Parts and Web Part zones.
• Content type: A reusable collection of settings to apply to a certain category of content such as documents and folders. Content types are designed to help users organize their SharePoint content in a more meaningful way.
• Custom action: Represents a link, toolbar button, menu item, or any control that can be added to a toolbar or menu that appears in the UI. We define custom actions by using a custom action element within a feature definition file. We can bind custom actions to a list type, content type, file type, or programmatic identifier (ProgID).
• Event receiver: Evaluator of an event and definer of the behavior of an application. Windows SharePoint Services 3.0 allows us to define event handlers within libraries, lists, and sites. Event receivers can be defined by using a receiver element within a feature definition file.
• Feature: A package of Windows SharePoint Services elements that can be activated for a specific scope and that helps users accomplish a particular goal or task. Windows SharePoint Services 3.0 introduces this inherently portable and modular functionality, which simplifies modification of sites through site definitions.
• Master page: Pages that provide a consistent layout and appearance (look and feel) for SharePoint sites. They allow us to factor out layout, structure, and interface elements such as headers, footers, navigation bars, and content placeholders. Master pages in ASP.NET 2.0 and master pages in Windows SharePoint Services work in the same way.
• Module: A file or collection of file instances that define the location where the files are installed during site creation. Modules are frequently used to implement a Web Part Page in the site. We can define modules by using a module element within a feature definition file.
• SharePoint site: A Web site hosted in a virtual URL. A SharePoint site is a place for collaboration, communication, or content storage. Depending on your business needs, we can create sites such as team sites, blog sites, wiki sites, and others. We can customize a site's appearance, users, user permissions, galleries, and site administration by using the Site Settings administration pages.
• SharePoint site collection: A collection of SharePoint sites that share common administration pages and site settings. Site collections allow you to share content types, site columns, templates, and Web Parts within a group of SharePoint sites.
• SharePoint Web farm: A group of Office SharePoint 2007 servers that share the same configuration database. All site content and all configuration data is shared for all front-end Web servers in a server farm.
• Site definition: A set of files that includes a master XML configuration file that is stored on all front-end Web servers. A site definition provides the basic blueprint for how sites look, what lists they include, their default navigational structures, and so on.
• Site template: A package containing a set of differences and changes from a base site definition that is created through the UI or through implementation of the object model. The site template package is stored as a .cab-based file that can be downloaded or uploaded to site collections by users with the appropriate rights. Site templates offer a measure of portability to SharePoint applications.
• Solution: A file that is a bundling of all the components for extending Windows SharePoint Services in a particular way. A solution file has a .cab-based format with a .wsp extension. A solution is a deployable, reusable package that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. We can use the solution file to deploy the contents of a Web Part package, including assemblies, class resources, and other package components.
• Theme: A group of files (CSS, images) that allow you to define the appearance (look and feel) of Web pages. Themes in ASP.NET 2.0 and themes in SharePoint Products and Technologies work in the same way. Themes are used to help organizations to brand their portals and team sites. Office SharePoint Server 2007 includes a set of predefined themes. However, as a developer, we can create custom themes for our company.