 |
| View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
| View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
 |
|
|
|
|
|
SharePoint for End Users > Categories
|
11/13/2009
The other day, a colleague of mine showed me a useful "SharePoint 2007 Permissions Matrix" on Mark Arend's MSDN blog. Mark's workbook helps show how permissions, permission levels, and groups relate and how they affect security trimming of Site Actions and Site Settings.
Now, I have to admit that I haven't taken the time to thoroughly verify all of the information in there, but I did scan both tabs and it looks like a good reference to get your mind around how things work or at least a useful starting point.
After agreeing to the download terms on the code gallery (code.msdn.microsoft.com), you can download the Excel workbook that contains the matrix. Here's the link:
Curl up around the fire with that this weekend and enjoy.
Matt Evans
SharePoint End-User Content Team 9/15/2009
by Rod Stagg, SharePoint Solutions Architect/Developer http://www.rstagg.com
Overview
We recently started an effort to provide a centralized and secure collaboration space for information sharing and collaboration across the enterprise using SharePoint 2007 and WSS.
The first phase of the project consists of a complete site redesign to provide the organization a consistent navigation and “Look and Feel” along with a consolidation of all existing SharePoint sites into a unified and secure SharePoint platform.
As part of the site redesign effort we investigated which approach would be most efficient for implementing the “Look and Feel” while also avoiding disrupting our existing WSS sites and users.
Technical Approach
The two primary choices for customizing the look and feel of both MOSS 2007 and WSS sites we evaluated were using custom alternate CSS stylesheets or using SharePoint themes. These choices would not require making significant changes to the sites' existing masterpages and templates. For our approach we decided to start with one of the existing SharePoint themes and customize it to match our branding.
What is a SharePoint theme?
SharePoint themes represent a collection of graphics and cascading style sheets that can modify how a Web site looks. Themes can be customized using SharePoint Designer or using the Visual Studio 2008 extensions for SharePoint.
Our customized theme for SharePoint 2007 and WSS sites look like this:
Advantages of using SharePoint themes:
- The SharePoint site settings interface provides the ability for both site administrators and site owners to customize the look and feel of their site by selecting from a pre-defined list of available site themes.
- The site settings interface provides the ability to display a preview/screenshot of the selected theme before they choose to apply it to their site.
- Themes can be easily removed via the SharePoint site settings interface.
- Themes packaged and deployed as a site feature simplify deployment across a SharePoint farm for IT administrators.
- Developers can take advantage of the set of ten Visual Studio 2008 extensions for SharePoint projects containing design themes for SharePoint provided by Microsoft as a starting point for developing a custom theme.
Applying a site theme:
Development of a custom site theme:
- Developers can install the set of ten Visual Studio 2008 extensions for SharePoint projects containing design themes for SharePoint provided by Microsoft as a starting point for developing a custom theme.
- You can download theme templates from: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0a87658f-20b8-4dcc-ad7a-09ad22641f3a
- Navigate to the installed theme folder (the default location is C:\Program Files\Microsoft\TenThemesForSharePoint)
- Open one of the Visual Studio theme solutions in Visual Studio 2008
- Modify the CSS classes directly in theme.css classes as needed.
- Drop in the necessary graphics/images into the projects local image directory.
- Build the project.
Source code for the customized version displayed above available by clicking the icon below.
Deployment
- Copy the Visual Studio project’s bin folder to your production server.
- Locate the setup.bat file in the debug folder.
- Open the setup.bat file in Notepad and modify the DefaultWebUrl and DefaultSiteUrl to point to the web application where you would like to install the theme.
- Save setup.bat and run as administrator.
- Navigate to a site and from the Site settings page select Site features, locate your theme and activate the feature.
- Open your portal site as Administrator and go to Site Actions>Site Settings>Modify All Site Settings. Under the Look and Feel Section, click on Site Theme and choose the newly installed theme.
9/10/2009
If you work with SharePoint records management solutions for a government organization, you might find the following resources to be helpful.
If you are interested in state and local government, check out this post about a time-saving county solution, which officials report has helped to improve response times and service to citizens.
Thanks,
Toni
SharePoint End User Content Team 8/27/2009
I’m pleased to announce that the fourth version of the Microsoft SharePoint Administration Toolkit is available for download! This is our last planned offering of new features and functionality for this toolkit that services both Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3.0. That said, we do plan to release a separate new toolkit for SharePoint 2010. With this release we added functionality to address various difficult administrative tasks. These include SharePoint Diagnostics Tool improvements, the Permissions Reporting Tool, the Quota Management command, and Security Configuration Wizard Manifests. Let’s look at these areas:
SharePoint Diagnostics Tool (SPDiag) update
The SharePoint Diagnostics Tool (SPDiag) version 2 contains several important updates and new features that increase its effectiveness as a troubleshooting tool. All SPDiag version 1 functionality has been retained, although some existing functions and features have been improved.
· A Diagnostics tab has been added which executes predefined rules designed to discover and report against some of the most common SharePoint issues.

· Command line data collection and data import has been added so that you can collect data from all servers in a farm for a given time range without installing the complete SharePoint Administration Toolkit on the target farm. The data can then be relocated to a remote computer and imported into a new project for offline analysis.
· Trend view zoom has been added to the performance monitor graph so that you can click and drag a specific time frame—updating all other frames to the new timeframe. Zooming out is as simple as a right click.
You can see detailed instructions on improvements on SPDiag on Microsoft TechNet:
· SharePoint Diagnostics Tool (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/dd745013.aspx)
· SharePoint Diagnostics Tool (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd745013.aspx)
Permissions Reporting Tool
In the past, customers have had a difficult time trying to detect what sites in a site collection have broken inheritance from the parent and thus why they cannot access some sites. The Permissions Reporting tool for SharePoint makes it very easy to detect where inheritance has been broken in a site collection. You can compare an object like a list or a site against its parent to see where inheritance was broken and run reports to get more information on such sites. You can also check effective permissions for a user or a group in a particular site, web, or list in a site collection; this feature lists the permissions that a user or group has.
Once the Permissions Reporting tool is installed in the farm, a site collection administrator can go to the top-level site or any subsite in a site collection and use the links on the Site Settings page to reap the benefits of the tool. The following image shows the new links that appear after you have installed the Permissions Reporting tool in the farm.

Note: To be able to see the links for Broken Inheritance Reports Jobs and Compare Permissions Sets, you must be a site collection administrator. However, anyone with the Enumerate Permissions permission — by default, people in the site Owners group — will be able to see the Check Effective Permissions link.
Click Broken Inheritance Report Jobs to run reports of broken sites in a site collection. Reports contain any information relevant to a broken inheritance. The report output is in XML, but you can save the files and then open them in Excel to see the information at a glance. For more information, see Run broken inheritance reports on Office.com.
Click Check Effective Permissions to check a user or group’s permissions on a site, list, or item. You can view what permissions are allowed and denied and any blocking permissions. For more information, see Check permissions for a user or group on Office.com.
Click Compare Permission Sets to compare an object such as a site or a list against its parent to quickly detect which object breaks inheritance in your site collection. For more information, see Compare permission sets on Office.com.
Quota Management
In the current version of SharePoint Products and Technologies, once a quota limit is applied to a site collection, the only way to change the limit is to manually update the quota limit for each site collection or write custom code. The updatequota operation the toolkit adds to stsadm does not have any parameters to globally set a quota limit change (that is, from 2 GB to 5 GB). The quota limit change is set by an administrator by using Central Administration Web site. Once the limit change is set, you then use the updatequota operation the toolkit adds to stsadm to apply the change to the specific site collections.
For example, you have a quota template named “Global” with a quota limit of 2 gigabyte (GB) that has been applied to 2,000 site collections. Currently, there is no automated way to modify existing site collections with this value. With the updatequota stsadm operation, the quota limit for all existing site collections using the Global quota template can be automatically increased or decreased as needed.
Security Configuration Wizard Manifests
Security Configuration Wizard (SCW) is an attack surface reduction tool introduced with Windows Server 2003 Service Pack 1. SCW uses a roles-based metaphor to solicit the functionality required for a server and disables the functionality that is not required. By automating this security best practice, SCW helps to create Windows environments that are less susceptible, on the whole, to security vulnerabilities that have been exploited.
For more information about the Security Configuration Wizard in Windows Server 2003, see the Security Configuration Wizard Documentation (http://go.microsoft.com/fwlink/?LinkId=162647).
The SCW manifests for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are included in the SharePoint Administration Toolkit v4.0. The manifests add the SCW roles for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 to Windows Server 2003.
For installation instructions, see
WSS: Installing the SharePoint Administration Toolkit (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc508987.aspx)
Installing the SharePoint Administration Toolkit (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc508849.aspx)
For more detailed information about the SharePoint Administration Toolkit, see following documentation on TechNet:
The download links for the SharePoint Administration Toolkit v4.0
x64: http://www.microsoft.com/downloads/details.aspx?FamilyID=665e98ea-5318-486d-aba2-2bfe46254357 (http://go.microsoft.com/fwlink/?LinkID=142035)
x86: http://www.microsoft.com/downloads/details.aspx?FamilyID=cd2d09a7-1159-4d40-be1c-8efab1345381 (http://go.microsoft.com/fwlink/?LinkId=141504)
Dan Winter
SharePoint Program Manager 8/19/2009
By Vicki Patel
Office Content Publishing
As a Site Owner, you have the ability to choose which permissions are associated with a particular permission level and/or add new permission levels to combine different sets of permissions.
I recently ran into an issue on our internal support site where contributors were accidentally deleting pages and content from the wikis. I wanted our wiki writers to have permissions to view, create and modify as needed. But I wanted to prevent them from deleting any wiki content. In order to accomplish this, I created a custom permission level and removed ‘delete’ as an option. Following are the steps to create a custom permission level and then apply it to a user/group for a site.
PART 1: Create a custom permission level on your site
- Click Site Actions, then Site Settings.
- Under Users and Permissions, click Advanced Permissions.
- Click Settings, and then click Permission levels.
On the Permission Levels page you can create a new level (where you manually choose all the appropriate fields) OR you can copy from an existing permission level from which you add/remove the specific permissions you want to make available to your users. The following steps show how to COPY from an existing permission level.
- Click the link for the existing permission level from which you will copy. (In this example I clicked Contribute).
- On the Edit Permission Level page for the group, scroll down to the bottom and click Copy Permission Level.
The page title should now read “Copy Permission Level … “.
- Enter the Name and Description you want to give your new permission level in the corresponding boxes. (For example, I entered Name = Contribute – No Delete in the Name box and Can view, add and update but not delete in the Description box.)
- In the Permissions section, review each of the checked boxes and select or deselect any of the check boxes as appropriate for your new permission level. For example, I deselected the check box for Delete Versions - Delete past versions of a list item or document.
- When you are done editing the new permission level, click Create.
- The new permission level will display in the list (see my example below).

- NEXT… apply your new permission level to specific users/groups on your site.
PART 2: Apply your new permission level to a specific users/groups on your site
-
Click Site Actions, and then Site Settings.
-
Under Users and Permissions, select Advanced Permissions.
-
Locate the User/Group in your list to which you want to apply the newly created permission level and select the check box. (In this example I’ve selected our team site permissions group called SOS Team Site – Contributor Perms.)
BEFORE
-
Click Actions, and then click Edit User Permissions.
-
Locate your new permission level under Choose Permissions and select the check box. Be sure to deselect any other permissions boxes.
-
Click Okay, which returns you to the Permissions page, and verify the new permissions are associated to your User/Group.
AFTER
Congrats! You’ve now created a new permission level, applied it to a user/group on your site, and have successfully customized your site’s permissions. For more information on managing permissions, see Manage Permission Levels 8/5/2009
By Mark Miller, founder and Editor of EndUserSharePoint.com
To celebrate the publication of the 1000th article on EndUserSharePoint.com, I talk about how the site was created, how it has become one of the most popular SharePoint communities on the internet, and how you might use those lessons on your own SharePoint site.
Overview
I get questions every week about how EndUserSharePoint.com has grown so fast. In less than 2 years page views and unique visitors have skyrocketed. Hundreds of people a month participate in the live online workshops. Because of this, I get asked for interviews from companies like MindJet, Bamboo Nation and EventBrite to talk about the work I’ve done to create such a community.
I’m just going to ramble for a couple minutes here to give you an idea on how all this came about and hopefully give you some ideas on how you can grow the audience for your blog or SharePoint site. Sit back, relax and enjoy the tangents.
How It All Started
When I started EndUserSharePoint.com I had a core group of people in mind that I wanted to reach: SharePoint End Users. As the site has progressed, I’ve broken that into three groups: Information Workers, Site Admin/Power Users and Site Collection Admin. If I were to be completely honest, I’d say that when I first started the blog, I was confusing Information Workers with End Users. SharePoint it so broad and deep, there are several levels of End Users, thus the differentiation.
A pyramid gives the best visualization of how I think about End Users of SharePoint. At the bottom of the stack is the Information Worker, the person who must use SharePoint because it has been mandated within the company. This is the broadest base of users of SharePoint, but the hardest to reach because they don’t care about SharePoint; they care about getting their job done. The technology doesn’t matter. “Just show me what to do and let me get back to my work.”
The second tier of users is the Site Admin/Power User. This is the group that has been “volunteered” to lead the charge on the use of SharePoint. In many cases, they requested access to a site for managing their projects or documents, IT told them that there was no such site available, but if they wanted one, they could have one. Sound familiar? You’re not alone because that’s the way most internal sites get started.
The third level of SharePoint End User is the Site Collection Administrator. Again, this person is usually forced into the position because in order for there to be sites, there must be a site collection.
I’ve heard all the talk about getting End User buy-in: “Manage your sites so it’s easy to find information”, “Get a good governance policy in place before you begin”, “Make sure you have a good Information Architect in place to build the hierarchy of sites”, “Provide great content to get people to come to your site”. Yeah, right, and while you’re at it, why don’t you bake me a cake, with my favorite frosting, but you’ve got to guess what kind of cake I like and what ingredients I’m allergic to when you make the icing. Come on, give me a break! I didn’t ask for this job. All I wanted was a place to put my documents.
Let’s get down and dirty here. You’ve got a site that you didn’t want in the first place, but now that it’s setup and part of your responsibility, you want people to use it. Who are you going to try to attract and why would they come?
Power Users: That’s Your Ticket In
The leadership today is about 10 people bringing you 100 and 100 bringing you 1,000. When you have 1,000 true fans, as Kevin Kelly talks about, then they're the people who are going to turn it into a movement. Not you. Your job is to take care of and feed and nurture those 1,000 people, and those people need to go to their network of people who know them and trust them, who eat dinner with them, and bring them in. -- Seth Godin
I like that, so I’ll repeat it again: Your job is to take care of and feed and nurture those 1,000 people…
Your job as a site manager isn’t to provide all the content for your site. Your job is to take care of and nurture those that will. That was one of my major epiphanies that changed the direction of EndUserSharePoint.com. I, Mark Miller, am nothing more, or less, that a content manager for authors who would like to give the community information about how to use SharePoint. I like to think that anyone who reads EndUserSharePoint.com on a consistent basis realizes the content is not from one source, but from a diverse group of authors who want to contribute to the growth and education of SharePoint Power Users and Site Administrators.
That leads me to the main point of this diatribe: The Site Admin/Power User is the group you need to get to for End User buy-in of your SharePoint implementation. By virtue of proximity to the site, they become the first line of support for Information workers, not the IT help desk, which probably doesn’t know much more than an average Power User anyway.
I used to think SharePoint Information Workers were the most critical to End User buy-in because they are the widest audience at the base of the pyramid, but I have changed my mind.
Power Users are great because of their need for immediate information. This is the main audience for EndUserSharePoint.com. We’ve setup a SharePoint Q&A forum for them that is moderated by other Power Users. We provide simple solutions in our articles to help them solve the interface problems that can get in the way of finding and managing information. The Weekly Newsletter provides free downloads for solutions that can be immediately implemented on a SharePoint site.
What we do on our site is something you might consider on your internal site: provide solutions to common problems that occur frequently enough that you’re tired of hearing about it! Where’s your list of common, reported requests? I’ve got reams of pages that I keep of ideas that are generated because the same questions keep coming up over and over. Until I discovered the power of OneNote, I was hitting Staples every couple months for a stack of yellow legal pads to keep my notes.
The questions that come at you as a Site Administrator can help you become more proficient at determining what your core audience is looking for.
Real World Story
When I started EndUserSharePoint.com, the purpose was to handle those day-to-day issues that Information Workers were running into when trying to get a handle on SharePoint; and that was the problem. My audience was extremely limited because Information Workers don’t want to get a handle on SharePoint!
SharePoint is just a tool Information Workers have to learn in order to do work they already do to their own satisfaction. “Why do I have to put this thing in this new location? We’ve already got a file server for that.” “My Excel sheets are working fine. I email them out every week and everyone is happy. Why in the world would I want to spend time putting that stuff in a new location?”
With a Site Admin/Power User, you’re not going to get that kind of push back. These people are your supporters. They want your SharePoint project to work. The problem is, there are usually no in-house resources to support them, there’s no budget to get training, there’s no line item in their job descriptions that says “Allocation of 10 hours a week towards SharePoint site management”, and a myriad of other things that make SharePoint life miserable at the company level.
Here’s a little secret for you: there’s tens of thousands of you out there! EndUserSharePoint.com started to take off when I realized that the audience who really cared about SharePoint, the hardcore evangelists, didn’t have a single point of resource to go to when trying to get information about a specific problem they were having. Once I recognized who the real audience was, it didn’t matter that the largest base of SharePoint End Users is the Information Worker. Those weren’t the people looking for help.
Let’s Do a Little Math
Microsoft tells us that there are 100,000,000 licenses sold for SharePoint. Whether you believe that number or not, is not the point. The point is there is a boatload of seats sold. What we have to think about from the EndUserSharePoint.com perspective is how many of those people are part of our potential audience. Keep in mind that we don’t do anything server related or programming related. “Deploy to the server” or “Put it in the GAC/12 hive/Whatchamacallit” doesn’t even exist in our world. If you want to talk about that stuff, don’t let the door hit you in the butt on the way out, because nobody here is going to understand a word you’re saying.
So let’s cutout 90% of the seats sold and we’ve still got 10,000,000 Site Admin/Power Users interested in SharePoint. Do you see where I’m going with this? Even after segmenting the market into different levels, there’s enough of the pie to go around. EndUserSharePoint.com was lucky to find the core audience and build from that, but there’s still so much headroom available, it’s almost unfathomable.
How does that relate to your situation as a Site Manager? To me, the little story above says “You don’t have to sell your site to the entire company. You have to sell it to the people that need it.”
Another Real World Story
I had a SharePoint site manager come to me and say “I’m pretty low in the corporate food chain in the overall scheme of things. This is a 7000 person company and my team is buried about 5 levels deep in the company hierarchy. How am I going to get buy-in from all those levels above me when I build out my SharePoint site?”
My answer: You’re not! Your core audience is the set of people who will be using your site on a daily or weekly basis, not the five levels of people above you. Get your house in order and then worry about the other guys. Create a site that is easy to navigate, easy to manage information flow and simple to maintain. Work with your team to get your site in shape so they can use it.
By doing that, you will create evangelists for your project, people who talk about it and sell it for you. Once people see what you are doing with your site, then you can start working with them to help build a consistent structure.
Yes, I know, people are going to scream “But Mark, how can you say that? We’ve got to have a governance policy in place before we can do anything. We’ve got to agree at a company level on how these things are going to work. You can’t just tell a site manager to go off on their own!”
Well, I’ve got news for you: In most cases it’s too late to do that. SharePoint is already out. People are already porting over content from their existing files servers by cutting and pasting entire hierarchical structures of folders and if you’re going to wait for all that to get hashed out before you start structuring your own share of the world, you’re going to be sitting there a pretty long time.
You’ve got to start somewhere. Why not in your own backyard? Clean up and structure to the best of your current knowledge and then start helping people around you. That’s a real Power User.
Where to Go from Here
I told you I was going to ramble a bit, but hopefully there are a couple tidbits for you to work with. The key is to find out who the core audience is, who will benefit the most from what you are trying to do. By concentrating on providing the most value you can for this audience, not only will your site be more useful, you will generate a core group of evangelists who bring more people to your site with their enthusiasm and belief in what you are doing.
Take a breath. Don’t be afraid to start. Someone is going to do it and it might as well be you.
About the Author
Mark Miller is founder and editor of EndUserSharePoint.com, one of the most popular sites for SharePoint End Users. He coordinates a group of a dozen contributing authors, managing the day-to-day aspects of editing and publishing content for the site.
When not teaching or writing about SharePoint, Mark can be found designing paper airplanes and studying the origami of Robert Lang. He lives in New York City with his wife, two children, one gerbil, one goldfish and one Nintendo DS that is constantly being fought over by the gerbil and the goldfish. 7/24/2009
I found a site that I think’s pretty cool, assuming you’re a SharePoint geek like me :-)
SharePoint Governance is quickly becoming an invaluable resource for info about how to effectively manage SharePoint sites, a.k.a. governance. It was launched on July 1st and contains info from your peers and “gurus”.
The site includes information such as, comparisons between SharePoint and other applications, how to setup a governance committee, and a SharePoint ECM governance plan.
I hope you find this helpful. See ya' next week.
Thanks,
Brian Granowitz
SharePoint documentation team 7/15/2009
by Mark Anable
Office Content Publishing
As we launched our internal MOSS site for the Office Content Publishing group, we wanted to have a place where users of the site could add suggestions for site features or other feedback. So, we created a simple feedback list. We added a link to the default new form for the list (newform.aspx) in the footer of the site so people could add new items no matter where they were on the site.
It worked great. People were using it, and we could use it to track and triage the site updates. However, the list had a lot of information that the users didn’t need when filling out a form – stuff that we, as site administrators, used to triage and track the items. Users needed only to add a title and description of their request – and not stuff like whether the request was accepted for triage and by what date we were estimating it could be done.
Not a problem, I thought. I opened newform.aspx for the list in SharePoint Designer, deleted the built-in form, and added Custom List Form. Then I removed the fields that I didn't want to show up in the UI. Now users didn't have to see these unnecessary fields but we could still use them to manage items.
Everything seemed to work well. But we would always open the list in a datasheet in order to do bulk changes. We never really edited items individually. Until one day I needed to open just one item to add a note. And I got an error:
An unexpected error has occurred.
Then, soon after that, one of the other admins needed to add another item to the list, so in the list she clicked New and got this error:
Invalid Page URL
We could still add items by going to the newform.aspx directly and by editing items in bulk mode, so this wasn't a blocking issue, but I could see this situation coming up later in more important and urgent scenarios.
I did some quick troubleshooting on a test list and found that the errors appear when you delete the default form for any of these files:
· DispForm.aspx
· EditForm.aspx
· NewForm.aspx
Furthermore, I learned that once you delete the default form there is no way to get it back. Undo doesn't undo. You have to recreate your list and move all of your data over to the new list.
A quick search revealed this Knowledge Base article, which says that instead of deleting the default form, you can hide the default form. To do that:
1. Start SharePoint Designer 2007, and then open the NewForm.aspx page for the list.
2. Right-click the List Form Web Part, and then click Web Part Properties.
3. Expand Layout, click to select the Hidden check box, and then click OK.
This blog describes some great in depth troubleshooting of this issue as well: http://blogs.msdn.com/dszabo/archive/2007/02/20/custom-list-newform-aspx-ruined-in-wss-3-0.aspx
So don't go deleting the default forms for your SharePoint Lists!
7/8/2009by Vicki Patel
Office Content Publishing
Keywords and Best Bets are manually configured by a site collection owner and are a great way to target important information in your search results. When a user enters in a pre-configured keyword into the search box, the best bets are displayed as part of the search results at the top of the page marked by a yellow star .
As a site owner on our internal team site, I configure best bets for terms on which our team members are searching. For example, I know that new hires to our group often search on the term permissions to find out how to get access to all the relevant tools and sites as part of our group. Because permissions is a word used in many documents, lots of results with the word permissions in them may be returned that are not relevant to new hires. So, we manually created a keyword and best bet term for permissions to ensure that the getting started info needed by new hires displays right at the top of our search page.
Defining a best bet for a keyword is easy to do. Just follow these steps.
Add your Keyword and Best Bets
-
Click Site Actions, then Site Settings, then Modify All Site Settings.
-
Under Site Collection Administration, click Search Keywords.
-
Note: If you do not have permissions to manage site collections, you will not have a Site Collection Administration option. See your site administrator for help.
-
On the Manage Keywords page, click Add Keyword.
-
Enter the search term you want to define in the Keyword Phrase text box. (i.e. in this example we are using permissions.) You may also want to enter a synonym in the Synonyms box, but this is not required.
-
Click the Add Best Bet link.
-
In the Add Best Bet dialog box, be sure Add New Best Bet is selected.
-
In the URL box, enter the URL of the page you want users to find based on the keyword you entered.
-
Enter a title for the best bet in the Title box.
-
Enter a description in the Description box. This is optional, but helpful to identify the purpose behind your best bet.
-
Click OK to close the dialog box. (Here is my best bet example for keyword = permissions)

-
On the Add Keyword page, you can enter the following optional information.
-
A contact who is responsible for the Keyword/Best Bet entered in the Contact box.
-
Under Publishing, add the Start Date (if later than the current date) and, if applicable, End Date (leave blank for no expiry), and Review Date.
- On the Add Keyword page, you can enter the following optional information.
- When you're done, click OK.
-
Next...test it out! In the search box for your site, enter your newly created keyword term, hit enter, and you should see at the top of your search results page your Best Bet -- a yellow star next to your Title, below that the Description, and then the URL link to your page. 6/26/2009
While surfing for cool content on this hot summer’s day, I came across Matthew McDermott’s SharePoint MVP profile. Turns out, Matthew and I share something in common besides SharePoint; we train dogs.
Matthew, and his dog Willa, founded K9 SEARCH, which serves the FBI, and Austin and San Antonio Police Departments. Looks like the K9 SEARCH website is running on SharePoint Server 2007. Pretty cool, on both counts, Matthew!
What do dogs have in common with SharePoint? It must have been this connection with dogs that led me to notice Matthew’s recommendation to HTML Dog: The Best Practice Guide to HTML and CSS, Patrick Griffiths' website and book.

As you'll soon find out, there’s nothing doggie about the HTML Dog website! From the Beginner HTML Tutorial to the more Advanced HTML Tags and CSS Properties references Patrick provides easy to read, step-by-step instructions, unraveling the seemingly deep, dark mystery about how HTML and CSS works. He augments the tutorials and references with articles, examples, and an invaluable list of external links.
As you may already know, when you view content on a Web page in SharePoint you’re looking at HTML and CSS that's coming from page templates and style sheets that reside on the front-end web servers (unless the page has been customized, but that's another story). The content is arranged on the page depending on the site template or the Web Parts in which it appears. If you're viewing content in a list or library you can change the way it looks by using a view.
Many of these choices are available “out-of-the-box,” but in most cases you can customize the look and feel of SharePoint. That means that the team site that I use does not look like the team site that you use.
We think this is cool, because, let’s face it, one size, color, and shape doesn’t work for everyone, right? But, it seems as though this confuses people. I think that’s where Patrick’s site can help. You don’t have to be an expert on HTML or CSS to use SharePoint, but it does help to understand the basics of what’s going on; especially if you’re a site administrator.
If you’re new to SharePoint or just need a good reference, give Patrick’s site a try. Thanks for the tip, Matthew. Just in time for the “dog days” of summer!
…Renée
SharePoint End-User Content Team
| View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/GetThePoint/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|
|
|