My new hero Adam Quinn snuck this brilliant sparkly gem into his NBSP post about calendar overlays and custom event content types. It rocked my world since I was unaware of this option and had been doing such a clunky way before! Just goes to show, always read through to the end of the post.
The prospect of something getting deleted from SharePoint can strike fear into the hearts of many users. So much fear, in fact, that they go to extraordinary lengths to try to make it so that no one CAN delete anything…. EVER. But think about it- SharePoint is not a catch-all or a bottomless archive. SharePoint is generally meant to hold active content that matters- in real time- to you and your colleagues. Sometimes people need to delete things. Sometimes people SHOULD delete things.
Don’t you know that SharePoint has your back? Use the tools at your disposal to ensure that you’ll never be the last to know when someone deletes a document or a list item, and give you ample chance to restore it if necessary.
“I can see the April TPS Report but my boss can’t!”
Guess what? Documents in a checked-out state are hidden from other users.
This simple solution is often overlooked. You may not even realize they are checked out. Rather than notice that the April TPS Report is checked out, you assume a permissions problem or other drastic reason. Trouble can come when well-meant efforts to “fix” the issue result in much more serious problems.
As a rule, the first thing end users should do in this situation is to determine whether the items in question are checked out. Check them back in, and voilà! Visible again.
Disclaimer: This article addresses the SharePoint 2007 Standard (WSS 3.0, not MOSS) environment. Some of my comments may not apply to other versions of SharePoint. Also, custom-developed solutions are not an option for any scenarios outlined in this article. I limit my approach to end user/power users who do not have
access to such resources.
Short answer: Nothing. The link was manually added to the Quick Launch. Manually-added links are not dynamically connected to the source list/library; therefore they don’t respond to such changes.
These have been stated by others, I am sure; but a recent training session led me to jot down a few things that stood out as just plain good ideas:
- Whenever possible- always create for re-use in the topmost site of the site collection (site columns, content types etc.).
- It can be so easy to get lazy or bow to the pressure of the squeakiest wheel to just get something done FAST.
- Take the time and do it right. Get good at speedy configuration of these items!
- When a list or library breaks permissions inheritance, or uses any advanced features that may affect display of content to end users, SAY SO in its description.
- I touched on this in a previous post, but it’s just a good idea. It informs everyone, from end users to support staff who need to know what about a particular content element may be different than the everyday OOTB configuration.
- Especially true of libraries where broken inheritance + versioning + content approval + layers of subfolders x cluelessness = ZOMG where’s the Advil.
- Whenever you can add a description to anything , DO IT. And make it worthwhile.
- This arose during a discussion of SharePoint group creation, and led to a deeper discussion around best practices of group set-up… which probably needs its own post later.
- This discussion included the need to expressly identify what a SharePoint group is for and what types or users are in it- meaning… DON’T simply leave the default group description text in there, for the love of God.
It has always baffled me why SharePoint offered a “Begins with…” filter parameter but did not offer “Does not begin with…” to meet the opposite need. Clare Stone offers a brilliantly simple solution to this aggravating problem in her Pentalogic SharePoint Blog post, “How to Create a SharePoint ‘Does Not Begin With’ Filtered List View.” Calculated columns to the rescue again!
I also recommend downloading their Calculated Column Cheat Sheet for a great resource to keep on hand when you’re stumped about calculated columns.