Force Left Nav To at least 200 Pixels wide
Force Body To at least 500 Pixels high
SharePoint MindsharpBlogs > Corro'll Driskell
iDeal Office Systems
Follow me @Twitter: @cdriskell

 Last 10 Posts

Dec 20


Corro'll Driskell

December 20, 2009

Happy holidays to all, I am Corro’ll (Corel) Driskell, a SharePoint Architect on the SharePoint platforms. As many of you know I do many things around the SharePoint platforms and found it difficult to pick a starting place since my involvement on the TAP program.

So, I wanted to kick off my blogs, referencing the SharePoint 2010 platform and its tools, with SharePoint Designer 2010 (Beta). I will post a number of blogs, as a part of this blog series, referencing the many features of SharePoint Designer 2010, such as, the new User Interface (UI), the ribbon, and a number of other features. Bottom line, this blog provides an overview focusing on the UI of SharePoint Designer 2010. This is not a deep dive into the capabilities of SharePoint Designer 2010 (BETA).

Microsoft SharePoint Designer 2010 (Beta) allows Designers – non-programmers - and, encourages, Developers, and I mean encourage, to build web based applications on SharePoint’s latest platforms (SharePoint Foundation 2010 and SharePoint Server 2010).

To start, you must locate SharePoint Designer 2010 in the Microsoft Office application group – its default location.


SharePoint Designer 2010 (Beta) UI 1

One of the great things about the, new, SharePoint Designer 2010 experience is the initial start. Immediately, the user (Designers and Developers) is provided visual feedback upon the start of the application. It is my experience that the loading is rather quick versus the experience with the previous version, SharePoint Designer 2007.


SharePoint Designer 2010 (Beta) UI 2

After SharePoint Designer 2010 (Beta) initially starts, you will notice that there are two primary focuses. The user has the option to Open a SharePoint Site or Create a New SharePoint Site. The new initial UI is a far step from the traditional experience of SharePoint Designer 2007. In fact, the user does not need to browse around the interface attempting to introduce them to the application. It is all there front and center.

In contrast, the fact that there is an option to use SharePoint Designer 2010 (Beta) on the My Site is discouraging. In another blog posting we will discuss the new features available on the, new, SharePoint 2010 platforms that afford the SharePoint administrators and Site Collection Administrator better control now is not the time to dive into those features, also, we will focus on the various options in more detail in a future blog as a part of this series.


SharePoint Designer 2010 (Beta) UI 3

After, either, Opening the Site or Creating a New Site, the user is presented with the Site Setting information page. Of course, the most notable change, in the SharePoint Designer 2010 UI, is the presentation of the, new, Ribbon. Again, I will dive deeper in the various features afforded by the Ribbon in a later blog as a part of this series.

The Settings Page provides a significant amount of information , such as, the Site Information, Permissions, SubSites, also known as Webs, Settings and Customization. The fact that this Designer Dashboard, yes, I called it a dashboard, and no it isn’t Microsoft’s official terminology, is forthcoming with quite a bit of information. This information was, either, lacking or wasn’t as easy to obtain in SharePoint Designer 2007. Again, we will dive deeper into many of the features during this series in a future blog. Although the tab interface is not new to SharePoint Designer 2007, I find the tab interface in SharePoint Designer 2010 (Beta) a bit more inviting and user friendly.


SharePoint Designer 2010 (Beta) UI 4

Lists and Libraries are nested in a simple view in SharePoint Designer 2010 (Beta). It is more similar to a report versus a hierarchical structure, as leveraged in SharePoint Designer 2007. Also, I want to encourage you to focus on the changes in the context of the Ribbon’s interface as we navigate from the Site Settings page. Of course, we can witness a heavy use of the bread crumbs in the SharePoint Designer 2010’s interface. The bread crumb was presented as a simple navigation control in the SharePoint Designer 2007 interface. Again, there was an emphasis on the hierarchical structure.


SharePoint Designer 2010 (Beta) UI 5

Workflows are also presented in a report form. The Workflows’ report provides summary information referencing workflows leveraged by the site or web. In the SharePoint Designer 2007 interface, Workflows were presented nested in a Workflow library or folder, depends on whom you ask. Again, there is an emphasis on the actual artifacts’ hosted on the SharePoint 2010 platform. Of course, there is a significant amount of new features for SharePoint Designer 2010 (Beta) and its capabilities to build flexible workflows. Again, we will dive deeper into those capabilities through-out this blog series.


SharePoint Designer 2010 (Beta) UI 6

The Site Pages provides summary information about located in the Sites Pages Library. The Site Pages Library is used to create and store pages for a specific Site or Web.


SharePoint Designer 2010 (Beta) UI 7

The Site Assets provides a reports view of files that are included on the pages of a Site or Web. In the SharePoint Designer 2007 UI, the storage locations for files included on the pages were stored in a number of locations, such as, the images folder.


SharePoint Designer 2010 (Beta) UI 8

The Content Types page provided a summary report about the various collection of content types, leveraged by the Site or Web, to establish consistent management of content. Immediately, you will find information, such as, Group, Parent, Source and Description. Most importantly, the UI provides quick access to manage the various content types. SharePoint Designer 2007 did not afford users this type of reporting feature. We will explore this new feature further as a part of this blog series.


SharePoint Designer 2010 (Beta) UI 9

The Site Columns UI provides a summary report referencing a collection of columns available to Lists, which includes, Column Name, Type, Group and Source. In the SharePoint Designer 2007 UI we did not have a central presentation of the linked columns for a Site or Web.


SharePoint Designer 2010 (Beta) UI 10

The External Content Types summary reports provides information, such as, Display Name, Name, External System, Type and Namespace, about External Lists, also known as SharePoint Lists, that exposes data from various back-end repositories – databases, web services and other Line-of-Business applications. The beauty of it all is that this feature is provided in the SharePoint Designer 2010 UI.


SharePoint Designer 2010 (Beta) UI 11

The Data Sources summary report provides information, Name, Type and Description, about the various data sources available to the Site or Web. The report is categorized based on type, for instance, Lists and Libraries. Again, this is a great presentation in the UI so that users are not required to leverage the hierarchical structure to obtain the information similar to the SharePoint Designer 2007 UI.


SharePoint Designer 2010 (Beta) UI 12

The Master Pages summary report provides information, Name, Title, Content Type, Size, Modified Date, Modified By and Comments, about all of the artifacts, Master Pages, Page Layouts, images and xml files, found in the Master Page Gallery.


SharePoint Designer 2010 (Beta) UI 13

The Site Groups summary report provides some information, Group Name and Description, about the various Groups with, some level, of access to the Site or Web. You have to ask yourself, where are the contributor settings. Again, we will dive deeper into the many changes in a later blog.


SharePoint Designer 2010 (Beta) UI 14

The SubSites summary reports provide a list of the Sites or Webs within the hierarchical structure. The report provides information, such as, Site Name, URL and Modified Date.


SharePoint Designer 2010 (Beta) UI 15

Finally, the All Files provides a summary report of all content for a Site or Web, which includes the SubSites. The information provided includes, Name, Title, Size, Type, Modified Date, Modified By and Comments. The significance here is users have a more efficient way to ascertain the information about the artifacts that make up SharePoint 2010 sites.


SharePoint Designer 2010 (Beta) UI 16

The overarching selling point is that SharePoint Designer 2010 encourages rapid building and deployment of, web-based, solutions that meet business needs, leveraging the various features – lists, content types, workflows and a number of other features – of an organization. Here is the catcher, there is no-coding. Included in this blog series, I will work to cover the various use cases and features.

Nov 16
Published: November 16, 2009 12:11 PM by  Corro'll Driskell

The Office SharePoint Foundation Server 2010 Beta (x64) and Office SharePoint Server 2010 Beta (x64) bits are now available on the Microsoft Technet site.  If you are not leveraging Microsoft’s Hyper-V, I would recommend leveraging VMware Workstation.  Microsoft Virtual PC – even on Windows 7 - does not support the 64 bit platform.  In fact, I don’t know how soon.


Get your SharePoint 2010 Beta bits here!

Nov 01

Over the last year, In evaluating many organization’s business needs and requirements, it was quite clear to me that SharePoint was not deployed as a content management platform. There were a number of reasons for this fact, but I will only focus on two. First, there was the lack of an organizational roadmap. The fact that many organizations failed to develop a formal roadmap, before deploying SharePoint, hindered user adoption and failed to align, the various features of, SharePoint with organizational business needs and requirements. Second and equally important, there was a lack of executive support and stakeholders involvement. To put it differently, IT was left holding the bag.

There are a number of questions as to where SharePoint sits in the enterprise as it compares to other content management (ECM, RM and DM) platforms. Naturally, many would expect for SharePoint to replace many of the existing ECM platforms. On the contrary, SharePoint – in many organizations – co-exist with a number of other content management platforms. Or, I have found that SharePoint is, either, competes or integrates with the existing content management platforms. This point is further supported by AIIM’s ( research; “State of the ECM Industry”.


Figure 8: Which of the following would you use to best describe your current or planned use of SharePoint in
your organization with regard to your existing ECM, DM and RM suite? N=233 (SharePoint users)

The question for many SharePoint Architects and Administrators is, “How do we overcome the SharePoint constraints?” Architects, administrators and consultants must clearly demonstrate a clear return on investment (ROI). But as insightful as that may be, it does not bear on the key issue at hand. The key issue is that decision makers do not view SharePoint as an enterprise solution in the content management space. As a result, senior management doesn’t view SharePoint as an organizational priority. It is my position that SharePoint 2010’s ECM features and Microsoft’s partner channel will fill in a number of gaps that would change senior management’s behavior. Today, SharePoint 2007 is an excellent choice as an organization’s ECM platform. But, an organization must build a formal roadmap for SharePoint.

In my next posting, I would like to take a closer look at SharePoint Governance and its value-add for building an ECM platform. Most importantly, leveraging a more structured approach to moving past a number of deployment road blocks.

Nov 01
Published: November 01, 2009 10:11 AM by  Corro'll Driskell

As a Learning Consultant, I have assisted a number of System Integrators (SI) with tightly aligning training with their overall fiscal goals.  Most importantly, we were able to measure the performance over time.  Also, I have consulted and trained on the SharePoint platform.  Over the several versions of SharePoint, I have found it to be amazing as to the salary ranges through-out the major cities.  The fact that I live in the Atlanta surrounding areas, I place an emphasis on it. 



On average, SharePoint consultants in the Atlanta area, yield about $100,000.  When you take a look at the cost of living for Georgia – specifically Atlanta – you will find that is a great salary.  In comparison to the standard of living as compared to other major cities, such as, Washington DC, Chicago, …etc.





The purpose of my blog is to encourage all to revaluate your training budgets and seek out training on the SharePoint platform.  I assert that Microsoft’s commitment to SharePoint is well founded.  Also, the next major version of SharePoint – SharePoint Foundation 2010 and SharePoint Server 2010 – is to beta this month.  Again, it is time to ramp up on various features available.  That is just my $19.11 worth.



Apr 04
Published: April 04, 2009 22:04 PM by  Todd Bleeker
Become a member of 'potentially, the largest SharePoint user group.  The purpose of UDiscover SharePoint is to remove the boundaries of brick and mortar style user groups.  The official launch date is February 25, 2009. 

Apr 03

There has been a number of conversations over the last year referencing building master pages from the bottom up using SharePoint Designer ( 2007). 

Although It is a best practice – using SPD 2007 -  to build customized master pages using an existing master page, it does not replace the fact that in order to recognize the various components that make up the master page a designer must build a master page from the ground up.

There are a number of blogs that speak to this process.  It is not my intent to duplicate any postings.  It is my intent to discuss this process in my own words and to add value based on the feedback from a number of sessions.  All designers, should download the base.master file from Microsoft and use it as a starting point. 

There are a number of blogs that identify the required controls and placeholders for Master Pages:

To start, I would recommend that designers open up a number of master pages in SharePoint Designer’s Code View.  You will note the consistent tags between  the <HEAD></HEAD> elements.  Remember, you would need to ensure that all of the required controls and content place holders are included on the master page. 


1.  You can copy the head elements of an existing master page.  That is a great way to avoid making mistakes.

<HEAD runat="server">
    <META Name="GENERATOR" Content="Microsoft SharePoint">
    <META Name="progid" Content="SharePoint.WebPartPage.Document">
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
    <META HTTP-EQUIV="Expires" content="0">

    <SharePoint:RobotsMetaTag runat="server"/>

    /*** Displays the set title for the site in the tile bar ***/
    <Title ID=onetidTitle><asp:ContentPlaceHolder id=PlaceHolderPageTitle runat="server"/></Title>

    /*** The CssLink control calls the core.css cascading style sheets from the WFE server’s 12 Hive ***/
    <SharePoint:CssLink runat="server"/>

    /*** The Theme control calls the cascading style sheet for the associated theme ***/
    <SharePoint:Theme runat="server"/>

   /*** The ScriptLink control runs the core.js javascript file.  It contains the basic SharePoint functions. ***/
    <SharePoint:ScriptLink language="javascript" name="core.js" Defer="true" runat="server"/>

    /*** Calls on any custom javascript files. ***/
    <SharePoint:CustomJSUrl runat="server"/>

    /*** Identifies the site’s disco file that defines the web services. ***/
    <SharePoint:SoapDiscoveryLink runat="server"/>

   /*** Content Place Holder that allows additional information to be added to the Page head. ***/
    <asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server"/>

   /*** SharePoint uses the DelegateControl to add additional content between the head elements. ***/
    <SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true"/>




2. Copy the opening body and form tags from an existing master page and overwrite open body and form tags.

<BODY scroll="yes" onload="javascript:if (typeof(_spBodyOnLoadWrapper) != 'undefined') _spBodyOnLoadWrapper();">
  <form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
    <WebPartPages:SPWebPartManager id="m" runat="Server"/>




3. In the event that you created a Master Page using the .masterpage template, delete the ContentPlaceHolder1 ContentPlaceholder & Save the master page.


<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server">




There are a number of Designers that would like to utilize absolute positioning to control the placement of objects on the master pages versus using tables. To be exact, Designers would like to get rid of the “SharePointy Look”.  No,…. the SharePointy term is not yet recognized by Wikipedia.  I could not resist adding a bit of humor to this post.

In order to leverage absolute positioning a Designer is required to do the following:

1. Wrap the PlaceHolders with DIV and SPAN elements.



2. Use a Cascading Style Sheet (CSS) to position the PlaceHolder on the page.




In the event that a Designer would like to leverage tables, there are a number of SharePoint Designer features that are available.

3. Click on the Table menu.




4. On the Master Page the Designer must identify the location of the Web Part toolpane.  By default, the Web Part toolpane is located in a table cell.  The MSO_ContentDiv is a placeholder control.  It’s purpose is to allow SharePoint  to add the web part toolpane.

<PlaceHolder id="MSO_ContentDiv" runat="server"></PlaceHolder>



Note: A Designer can use a table for formatting inside of the MSO_ContentDiv PlaceHolder.  The default.master file provides a great example.

Note: The primary PlaceHolder used out of the box is the PlaceHolderMain.  Within the PlaceHolderMain elements a Designer can use a table to layout the content in that area.

5.  For all placeholders that are not used by the Designer, it is recommended that the Designer use the Panel control to hide the un-used placeholders.  A Designer’s other option would be to set the visible property to false for each placeholder.

<asp:panel visible="false" runat="server">
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderBodyRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderCalendarNavigator" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderFormDigest" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderHorizontalNav" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftActions" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBar" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBarDataSource" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBarTop" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleBreadcrumb" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleInTitleArea" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderPageTitleInTitleArea" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTopNavBar" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderUtilityContent" runat="server" />
<asp:ContentPlaceHolder ID="SPNavigation" runat="server" />
<asp:ContentPlaceHolder ID="WSSDesignConsole" runat="server" />
<asp:ContentPlaceHolder ID="OSSConsole" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat="server"/>                       

This is just a start.  I encourage you all to look out for Enrique Lima’s posting over the next few days.  I will update this blog with a reference to his detailed steps for, “Building a Master Page from the ground up”.

Feb 19
Published: February 19, 2009 14:02 PM by  Corro'll Driskell


During a number of facilitated sessions, I mention a number of resources that all SharePoint designers must reference.  I have included a reference to those resources in this blog.  I will update this blog post with additional information on a consistent basis.  Please continue to add value by posting additional references in you comments.

Disclaimer: I am not personally responsible for the content of the listed resources. 

In order to properly customize a SharePoint platform.  It is my position that all designers must have a basic knowledge of SharePoint.  I have included some links to introduce you to the SharePoint platform and its offerings.

An Introduction to Office SharePoint  2007

Microsoft Test-drive –  (You need to sign up for this.)

Virtual Lab: SharePoint Products and Technologies

Although the use of SharePoint Designer 2007 doesn’t require knowledge of code, I strongly believe that all designers should learn about XML, HTML and CSS.  There is a significant value in reviewing the following links:

XML, HTML, and CSS resources:

W3C MarkUp Guide

Introduction to CSS2

XML Schema Part 0: Primer Second Edition

CSS Classes in SharePoint’s core.css

CSS Zen Garden – some great examples of what can be done with CSS

World Wide Web Consortium (W3C) recommendations for XPath  (version 2.0)

Surfacing CSS Classes in SharePoint Pages

In order to ensure that an organization follow organizational and government policies, SharePoint designers must ensure that they are knowledgeable about accessibility and how SharePoint Designer adds value.  It has become more important for organizations today to include accessibility in their project plans.

Accessibility of SharePoint Sites:

Tips for Enhancing the Accessibility of SharePoint Web Sites

Section 508 VPATs for Microsoft products

Additional Workflow tools:

Windows SharePoint Services 3.0 Starter Kit: Workflow Developer Starter Kit for Windows SharePoint Services 3.0

Note:  The Workflow Developer Starter Kit for Windows SharePoint Services 3.0 (WSSWorkflowStarterKitB2.msi) templates are now part of the Windows SharePoint Services 3.0 Software Development Kit (WssSdk.exe).

Software Development Kits:

Windows SharePoint Services 3.0 Software Development Kit

SharePoint Server 2007 SDK: Software Developer Kit

Design Policies and Templates:

 Office SharePoint Server 2007 Customization Policy
by Sean Livingston

WSS 3.0 Master Pages and Content PlaceHolder’s: A Desktop Reference Companion

MOSS Navigation Deep Dive – Part 1

Other Resources:

Adding the Edit Button to the IE7 Toolbar:
by Kathy Hughes

How to configure form results and have them sent to multiple email addresses?

Customizing the menu control for MOSS

Overview of Field Controls

Stramit SharePoint 2007 Master Picker

Search Resources

Google Code Search

Discover SharePoint


Feb 18
Published: February 18, 2009 22:02 PM by  Corro'll Driskell

There are a number of blogs that focus on configuring ( Create a Contributor group) the the Contributor Settings in SharePoint Designer 2007.  It is not my intentions to provide the step by step to create and configure contributor settings. 

Site Menu in SPD

Also, I can site a number of sites that clearly define the intentions of Contributor Settings (Introduction to Contributor Settings).  In summary, the intent of the Contributor Settings is to control the use of SharePoint Designer on a site by site basis. 

Contributor Groups of Contributor Settings

I am posting this blog to discuss the limitations of the Contributor Setting configurations and proposed work around. The fact that contributor settings are configurable on a site by site basis is not a great option in a number of site deployments.  The fact that new sites are created within site collections at an alarming rate, is a compelling reason to ask for more of a centralized capability to set the contributor settings at the site collection level and to push it down throughout its namespace.  In fact, it would be great to ensure that all sites across all web applications - scoped at individual sites - are dynamically configured with the required contributor settings.

The fact remains that Contributor Settings can only be set by using SharePoint Designer as the Site Manager.  After the [contributor setting].htm - generally named using the GUID of the site - is created, the [contributor setting].htm can be added to a site template using the File element in the ONET.XML file. 

Contributor Setting File

But, in the event that Designers do not have access to the Web Front End (WFE) servers, adding the [contributor setting].htm as a file element to the ONET.XML file, is not a viable option.

What we have found that adds some value for our SharePoint Designers - using SharePoint Designer 2007 - is that you can create a site - using the Browser or SharePoint Designer 2007 as a tool.  After creating and customizing - it is titled Branding in some eyes - the site. 

Once the site is customized, the Site Manager can create Contributor Groups and Region Types.   After configuring the Contributor Settings, the Site Manager, Site Owner or Site Collection Owner - that all depends on the level of the site and the tools - Browser or SharePoint Designer - can save the site as a template. 


Site Template Option Using SPD Site Template Option Using Browser

Site Template Options


To ensure that the save template(s) are used, the Site Collection Administrator or Site Owner can limit the template choices to the template(s) configured with the Contributor Settings.



The option presented is not the most centralized way to ensure the use of a consistent contributor settings across a number of sites within a site collection.  But, it presents an option to ensure the authorized use of SharePoint Designer 2007 on each sub-site.

I hope that this helps.....

Dec 11
Published: December 11, 2008 18:12 PM by  Corro'll Driskell

There are a number of requests in regards to rolling up calendar events from various sites to a site hosting a master calendar.  The most economical choice is to use SharePoint Designer 2007.

 "This post, only, focuses on creating linked calendars." 
1.  You will need to open up the site that will host the master   calendar.  After selecting the URL for the hosting site, Click on the Open button.


2.  After the web site is opened in SharePoint Designer you will see all related folders and files displayed in the Folder List.
3.  Click on the Task Pane menu and Select the  Data Source Library. The Data Source Library is displayed.

TaskPane_DataSource DataSourceLibrary

4. From the Data Source Library task pane, select Connect to another library... the Manage Library dialog box appears.  Click on the Add button.

Connect to library


5. The Collection Properties dialog box is displayed.  In the Display Name text box, type the name of the site.  In the Location text box, type in the URL for the source site.  Click on the OK button to close the Collection Properties and Click the OK button to close the Manage Library dialog box.


 Note: The new Collection - IT Services - is available from in the Data Source Library.


6. In the Data Source Library task pane, navigate to the Current Site Collection .  Click the plus symbol next to Current Site.  Next, Click the plus symbol next to the Linked sources and Click Create a new linked source… button. Next, Click on the Configure Linked Source... Button.



7.  The Link Data Sources Wizard dialog is displayed.  In the Available Data Sources list box, ensure that the Current Site Collection data sources are displayed.  Next, Click on the SharePoint Lists and select the Calendar list.  Next, Click on the Add button.


8.  In the Available Data Sources list box, Click on the IT Services Collection's data sources are displayed in the Available Data Sources.  Next, Click on the SharePoint Lists and select the Calendar list.  Next, Click the Add button.  Finally, Click on the Next button.


9.  In the 'Select the link type that best represents the relationship between the selected sources' section, Select the option, 'Merge the contents of the data sources.  Choose this option if you'd like to sort, group, and filter the sources as one long list.'  Click the Finish button. 


10.  The Data Source Properties are displaying the added Calendars in the Component source properties section.  Click on the OK button.


Note: After the Linked Data Source is saved, it is named New Data Source in the Linked sources section.


11. Using SharePoint Designer, Create a new ASPX page in the current site.  Click in the Form control to position your cursor.


12.  Click on the Data View menu.  Next, Click on Insert Data View.. option.  The DataFormWebPart is added in the Form control.



13.  Navigate to the Data Source Library task pane. Drag and drop the merged calendars - New Data Source - onto the DataFormWebPart on the new page.


14.  Click on the 'On Object User Interface' (OOUI), It will open the 'Common Data View Tasks'.  Click on the Edit Columns.. option.


15.  Remove both Modified By and Modified from  Displayed Columns list box and add Location field from the Available fields list boxNext, Click on the OK button.

 DataFormWebPart_EditColumns DataFormWebPart_EditColumnsResults

16.  Navigate back to the Common Data View Tasks properties.  Click on the Filter option.  Use the table below to configure the filters. After configuration, Click the OK button.

Field Name
Start Time
Greater Than or Equal To
[Current Date]
End Time
Greater Than or Equal To
[Current Date]


17.  Save the page and preview in the browser.  You can add events to all calendars included in linked sources and it is reflected in the rendered page.
Note: You can attach the page to the master page for the site to ensure that it is branded like all other pages.

Nov 28
Published: November 28, 2008 22:11 PM by  Corro'll Driskell
Enterprise Features
Enable Enterprise features
In the event an administrator decides to install Microsoft Office SharePoint Server 2007 by using the Standard license type, the following features are available:
Enterprise content management
My Sites
Profiles and personalization
Enterprise search

On the other hand, a SharePoint Administrator can convert the license type to the Enterprise license, which would enable and, allow the SharePoint Administrator to push down the Enterprise feature set to all sites within a server farm. The following additional features, in conjunction with the Standard license features, are available with the Enterprise license type:
Business Data Catalog
Excel Services
Report Center
InfoPath Forms Services

Enable Enterprise features
In Central Administration, on the Operations tab, under Upgrade and Migration, click Enable Enterprise Features.
On the Enable Enterprise Features page, under Use these features, click Enterprise (Requires Enterprise client license).

In the Enter Product Key box, type the Enterprise Client license key.
Important You cannot return to using the Standard feature set after you have enabled the Enterprise feature set. If you want to return to using only the Standard features, you must turn off all of the Enterprise features on all sites. Alternatively, you can uninstall Office SharePoint Server 2007, reinstall it by using the Standard license type and create a new server farm, and then attach the content databases to the new farm. BTW, bad, bad, bad….
Enable features on existing sites
In Central Administration, on the Operations tab, under Upgrade and Migration, click Enable Features on existing sites.

On the Enable Features on existing sites page, select the Enable all sites in this installation to use the following set of features check box.

After enabling features for all sites, you will note the enabling status displaying a status of Initializing.
In essence, the configuration of the features allows a SharePoint Administrator to manage the features at both the Farm and Web Application level.

Manage Farm Features

Manage Web Application Features

 ‭(Hidden)‬ Admin Links