I wanted to display just the year of a DateTime column of SharePoint. I created a calculated column and set the formula to Year([MyDateTimeColumn]). The result I got was 2,009 ; 2,008 etc. which offcourse incorrect for year. After searching through internet, I found a good article solved my problem.
The correct formula is TEXT(YEAR([MyDateTimeColumn]),”000″)
If you want to set a custom edit form to your Sharepoint List then please make sure you follow these Golden Rules as correctly suggested by Hugo in a SharePoint news group.
These rules are real time savers and I will highly encourage every reader to follow them.
It is natural to assume that if you have Modify permission on any SharePoint item/document then it means you can update any property of that document, right? Wrong! You can update any property of a document/item except Name property. This is because in SharePoint terms, changing the name of the document means two things:
If you don’t have Delete permission and just have Modify permission then you can modify every property except the Name property.
So, if you are getting Access Denied error while changing the Name of a document of a SharePoint Documnt Library and you know that you have the Update/Modify permission on that doucment then make sure you also have Delete permission on that document.
Ten new SharePoint themes have been released by Microsoft to help SharePoint designers to make new sites more efficientlty. You will find them as individual Visual Studio 2008 projects which when deployed to SharePoint offer fresh new designed themes you can use in your projects.
Themes can be downloaded from here
Following is a preview image of these themes (from Sharepoint.microsoft.com)
A goow news for SharePoint community 
Microsoft has releasesd the Mar 2009 CTP of Windows SharePoint Services 3.0 v1.3. This CTP contains excellent set of functionalities and saves your precious time. You can download the extensions from here
Following is the overview as released by Microsoft
This is the SharePoint developer tools for Visual Studio 2008. These tools are suitable for use with Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007. It includes project and item templates for common SharePoint artifacts, it includes build, packaging and deployment for SharePoint solutions and it includes the SharePoint Solution Generator which creates a new Visual Studio 2008 project from a SharePoint site.
The tools provide item templates for List Definition, List Definition from Content Type, Content Type, Field Control, Web Part, Module, Root File, Template, Event Receiver, and List Instance. It provides project templates for Team Site Definition, Blank Site Definition, List Definition, Web Part and Empty. It works with Visual Basic .NET and C# languages and a comprehensive user guide is included. It does not include the SharePoint Workflow templates as they are built in with Visual Studio 2008.
New features in version 1.3 include:
Business Problem:
One of my client wanted to have links on main portal to launch Microsoft Office key applications i.e Word, Excel, Power Point and Outlook directly by clicking on a link at portal page.
Solution:
I searched the net and find a nice solution here It is a small piece of JavaScript code which you can put in CEWP and use it on your portal page. I added some formatting and relevant icons against the office applications and wraps it up in a webpart dwp file. After importing this web part on your page, you will get something like this:
You can download the dwp file from here
If you are getting “Cannot run Windows SharePoint Services on this page…” error while trying to upload multiple files in Sharepoint and you are banging your head against the wall then don’t worry you are not alone It is the shared pain by many of us facing the legacy errors of FrontPage Server extensions in Sharepoint. This error occurs if you modify Upload.aspx located in layouts folder. First and foremost, do not modify the standard upload.aspx or any other standard file in Sharepoint as it is not supported by Microsoft and your change will be overwritten by any new service pack or hot fix.
So having said that, if you have made a copy of upload.aspx, customized it and trying to use it then you may certainly face this error. Following is the solution to fix it:
<input TYPE="hidden" NAME="_charset_" VALUE="utf-8"><!--webbot bot="FileUpload" endspan i-checksum="45034" --><input TYPE="hidden" NAME="Cmd" VALUE="Save"><!--webbot bot="FileUpload" endspan --> :):)
Following is a list of tokens available in Sharepoint to use in your URLs. Be aware that Sharepoint only replaces the value of a token once for a given string, so if you have used the same token twice, second occurance will not be replaced by the token value. I will post a solution to do it in my next article:
~site – Web site (SPWeb) relative link.
~sitecollection – site collection (SPSite) relative link.
In addition, you can use the following tokens within a URL:
{ItemId} – Integer ID that represents the item within a list.
{ItemUrl} – URL of the item being acted upon. Only work for documents in libraries. [Not functional in Beta 2]
{ListId} - GUID that represents the list.
{SiteUrl} – URL of the Web site (SPWeb).
{RecurrenceId} – Recurrence index. This token is not supported for use in the context menus of list items.
If you are like me and trying to customize the search result presentation in SharePoint then you must have faced the issue of customizing the XSL of Sharepoint Search Core Results Web Part. You can customize the XSL by using SharePoint Designer or any other WYSIWYG XSL editor, if you know the raw XML returned by Search.
To get the raw XML click XSL Editor button of Search Core Results web part and replace the already provided XSL with the following
<xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” >
<xsl:output method=”xml” version=”1.0″ encoding=”UTF-8″ indent=”yes” />
<xsl:template match=”/”>
<xmp><xsl:copy-of select=”*”/></xmp>
</xsl:template>
</xsl:stylesheet>
RSS Feed
