Skip to main content

SharepointLabs.com Blog on MOSS - WSS 3.0 sharing experience, technology, news, views and more

Go Search
Home
Buy Webparts
SharePoint Training
Contact Us for Consulting Inquiry
  

SharepointLabs.com Blog on MOSS - WSS 3.0 sharing experience, technology, news, views and more > Categories
Free Timezone Converter Webpart by SharePointlabs.com released

We are pleased to announce that we have now launched new TimeZone Converter webpart for everyone for FREE.

This is business essential webpart and what more you can offer but to be released as FREE.

Visit http://webparts.sharepointlabs.com/time-zone-wepart.htm to review and download it now.

SharePoint Time Zone WebPart helps user to convert time from one time zone to other time zone.   Sharepoint Time zone webpart is basic webpart to convert time from one time zone to other time zone rather than looking into system watch or surfing on time zone conversion web site.

SharePoint Commerce Services and Webparts (Commerce Server 2009 and SharePoint)

Microsoft Commerce Server 2009 (http://www.microsoft.com/commerceserver/en/us/default.aspx ) ready to go shopping ecommerce website solution which is also a collection of over 30 SharePoint Webparts which can be combined and deployed on a SharePoint site to provide a full e-commerce retail-shopping site. To gather these webparts and commerce server 2009 provides solution a full e-commerce site. These 30+ webparts are implemented using SharePoint Commerce Service.

The available Web Parts fall into six categories:

  • Catalog Web Parts display available products or services
    • Images Viewer Web Part
    • Product Details Web Part
    • Product Query Web Part
  • Marketing Web Parts manage advertisements, special offers, and other marketing programs
    • Discount Ad Web Part
    • Reviews And Ratings Average Rating Web Part
    • Reviews And Ratings List Web Part
    • Store Locator Web Part
  • Orders Web Parts handle ordering of products or services
    • Add to Cart Web Part
    • Checkout Web Part
    • MiniCart Web Part
    • My Lists Web Part
    • My Lists Detail Web Part
    • Order Details Web Part
    • Order History Web Part
    • Shopping Cart Web Part
  • Profile Administration System Web Parts contain information about customers
    • Address Book Web Part
    • Address Detail Web Part
    • Change Password Web Part
    • Credit Cards Web Part
    • Credit Card Detail Web Part
    • Forgot Password Web Part
    • Live ID Feature
    • My Profile Web Part
    • Registration Web Part
  • Management Web Parts add management capabilities
    • Channel Configuration Feature
    • Inline Product Property Editor Web Part
    • Product Provider Web Part
    • Simple Property List Web Part
  • Search Web Parts handle the search feature
    • Search Box Web Part
    • Search Paging Web Part
    • Search Results Web Part

So on concluding note Microsoft Commerce Server 2009 is more than just a e-commerce platform—it's the foundation for a new way to conduct business online. Get a contemporary site up and running out of the box and make real-time adjustments with the click of a mouse. Take advantage of near seamless integration with Microsoft Office SharePoint Server 2007, or explore the many new ways to build deep, lasting connections with shoppers with our Web 2.0 features. By providing the flexibility of a software solution with the power of an integrated platform, Commerce Server 2009 is built to suit your business.

Microsoft Commerce Server and out of box 30 SharePoint Webparts

Microsoft Commerce Server is a Microsoft product for building e-commerce systems. It uses Microsoft .NET technology. Commerce Server 2009, which became available on Microsoft's price list on April 1, 2009, introduced multi-channel awareness into the product, a new default site (running in Microsoft's SharePoint product) - including 30 new web parts and controls, and WYSIWYG (what-you-see-is-what-you-get) editing experiences for business people and site designers. Commerce Server 2009 adds the following functionality:

  • Multi-channel awareness.
  • Additional shopping features
  • Default Web Site.
  • 30 Web Parts and Controls. Collectively known as the Microsoft SharePoint Commerce Services, Commerce Server 2009 ships with over 30 different Web Parts and controls that, when assembled within SharePoint, give you contemporary e-commerce Web site functionality. The Web Parts are categorized into the following groups of functionality: Marketing, Search, Orders, Catalog, Profile Administration, and Management.

These key features were introduce through the new Commerce Foundation - a new abstraction layer which unifies calling patterns of the core systems (see below) and allows for different presentation and business logic to be easily added and represented as 'selling channels'; and SharePoint Commerce Services which includes integration with Microsoft SharePoint - a new default site with 30 new web parts and controls pre-assembled. The default site can be easily skinned through the new page templating technology, allowing for individual pages to be easily changed by selecting a different template.

Commerce Server still retains its core systems of Catalog, Inventory, Orders, Profiles, and Marketing

Following is the list of SharePoint webparts available out of box for Commerce Server 2009

Sl. No

Name

Description

1

Address

A web part that provides address manipulation capabilities.

2

Address List

A web part which provides a list of addresses.

3

Add To Cart

An Add To Cart Web Part for Commerce Server 2007.

4

Advertisement List

A Web Part that displays advertisements/discounts

5

Shopping Cart

A Shopping Cart web part for Commerce Server 2007.

6

Change Password

A Web Part that provides users with the ability to change their passwords.

7

Checkout

A checkout web part for Commerce Server 2007.

8

Content Query

Use to display a dynamic view of content from your site on a web page

9

Credit Card

A web part which provides credit cards manipulation.

10

Credit Card List

A Web Part that provides a list of credit cards.

11

Forgot Password

A Web Part which provides the user the ability to recover their password.

12

MiniCart

A mini shopping cart web part for Commerce Server 2007.

13

XML Web Part

Use for XML, and XSL Transformation of the XML.

14

My Profile

Use to display a shopper's profile.

15

My Shopper Lists

A My Shopper lists web part for Commerce Server 2007.

16

Order Details

An order details web part for Commerce Server 2007.

17

Order History

An order history web part for Commerce Server 2007

18

Product Details

Used to display product properties of a web part through XSL transformations

19

Product Filter

Used to filter the contents of another web part for the catalog and product in the URL.

20

Product Provider.

Used to retrieve a product.

21

Product Query

Used to retrieve a collection of products.

22

Reviews and Ratings - Average Rating

Displays the average product rating

23

Registration Wizard

Allows for the Registration of new users.

24

Reviews and Ratings - List

Displays a list of product reviews and ratings

25

Search Box

A web part which conducts catalog and/or static contents search

26

Search Paging

A web part iterate through catalog and/or static contents search results on Search Results web part

27

Search Results

A web part which displays catalog and/or static contents search results

28

Shopper List Detail

A shopper list detail web part for Commerce Server 2007

29

Simple Property List

Used to display properties of a product.

30

Store Locator

A Web Part that allows user to pick nearest store on a virtual earth map

31

Summary Link

Use to display links on your web page that can be grouped and styled and can be organized by dragging and dropping

32

Table Of Contents

Use to display the navigation hierarchy of your site on a web page

 

WSS HotFix

http://support.microsoft.com/kb/934790


This hotfix package fixes the following issues:

934253 (http://support.microsoft.com/kb/934253/) The Web File Properties dialog box displays incorrect properties for a document that is saved in a Windows SharePoint Services 3.0 document library

934882 (http://support.microsoft.com/kb/934882/) A file that is attached to an e-mail message is not put in a Windows SharePoint Services 3.0 document library

934613 (http://support.microsoft.com/kb/934613/) Error message when you try to install a feature in Windows SharePoint Services 3.0: "The 'UserSelectionMode' attribute is not allowed"

935605 (http://support.microsoft.com/kb/935605/) Issues that may occur when you use the volume shadow copy service (VSS) reference writer in Windows SharePoint Services 3.0
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
• You add two List Web Parts to a page of a Windows SharePoint Services 3.0 Web site. The second List Web Part is connected to receive data from the first List Web Part. When you click the option button for an item in the first List Web Part, only that list item appears in the second List Web Part as expected. However, if you sort the results of the first List Web Part and then click the option button for a different item in the list, all list items unexpectedly appear in the second List Web Part.
• You run an SQL query to change the properties for a user that you created on a Windows SharePoint Services 3.0 Web site. When you run the PeoplePicker tool to search for a user, the original user is unexpectedly found. You would expect the PeoplePicker tool to use the changes that you made to the user's properties when it searches for a user.
• You browse a Windows SharePoint Services 3.0 Web site that contains different language subwebs. When you search one language subweb for an item that does not exist, you receive an error message as expected in that language subweb. However, when you search for an item that does not exist in a different language subweb, you unexpectedly receive an error message in the first language subweb that you searched.
• When you use the ItemAdding event to add a new file to a Windows SharePoint Services 3.0 document library, the path of the document library folder cannot be found.
• When you upload a file to multiple Windows SharePoint Services 3.0 document libraries, an alert creation e-mail message is sent from the document libraries as expected. However, an alert notification e-mail message is sent from only one document library. You would expect an alert notification e-mail message to be sent from all the document libraries to which you uploaded the file.
• When you run a program that uses the SPWorkflowManager.ForceDehydrateHttpContextWorkflows() event to work with files that are saved in a Windows SharePoint Services 3.0 document library, the expected Web page is not displayed. Additionally, you receive the following error message:
Service Unavailable
• If you set the Hint property of a Full Text Query object to OptimizeWithFullTextIndex and then query the computer that is running Windows SharePoint Services 3.0, the order of the results is sorted incorrectly.

Posted by Vaibhav Jain (Success is always one step ahead)

Filter list view using invisible webpart where list will get filter according to current logged in user : wss 3.0 (SPQuery)

In below code case is : we have "method type" field in list methods are method1,method2, method3. Now for each method we have separate groups and if you want to filter view according method for logged in user then create one webpart without interface and place this webpart on just above list view webpart on screen and debug check filteration.

using System;
using System.Collections.Generic;
using System.Text;
using System.Web;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;

namespace ViewWebPart
{
public class ViewOnRights : System.Web.UI.WebControls.WebParts.WebPart
{

protected override void Render(System.Web.UI.HtmlTextWriter writer)
{
SPSecurity.RunWithElevatedPrivileges(delegate()
{
SPWeb w = SPContext.Current.Web;
SPUser currentUser = w.CurrentUser;

if (!currentUser.IsSiteAdmin)
{
using (SPSite ElevatedSiteColl = new SPSite(w.Site.ID))
{
SPUser targetUser = ElevatedSiteColl.SystemAccount;
SPUserToken token = targetUser.UserToken;
using (SPSite SiteColl = new SPSite(ElevatedSiteColl.ID, token))
{
using (SPWeb web = SiteColl.OpenWeb(w.ID))
{
web.AllowUnsafeUpdates = true;

string method1 = string.Empty;
string method2 = string.Empty;
string method3 = string.Empty;
string strQuery = string.Empty;

SPGroupCollection userGroups = currentUser.Groups;
foreach (SPGroup grp in userGroups)
{
if (grp.Name.Substring(0, 3).ToLower().Equals("method1"))
{
method1 = "method1";
}
else if (grp.Name.Substring(0, 7).ToLower().Equals("method3"))
{
method3 = "method3";
}
else if (grp.Name.Substring(0, 8).ToLower().Equals("method2"))
{
method2 = "method2";
}
}
SPQuery query = new SPQuery();
strQuery = "";
strQuery += "" + method1 + "";
strQuery += "" + method3 + "";
strQuery += "" + method2 + "";
strQuery += "";

query.Query = strQuery;
SPView view = web.Lists["List name on which you want to do filteration"].Views["All Items"];
view.Query = query.Query;
view.Update();

if (Page.Session["User"] == null)
{
Page.Session["User"] = currentUser.LoginName.ToString();
Page.Response.Redirect(Page.Request.Url.ToString());
}
else if (Page.Session["User"].ToString() != currentUser.LoginName.ToString())
{
Page.Session["User"] = currentUser.LoginName.ToString();
Page.Response.Redirect(Page.Request.Url.ToString());
}
}
}
}
}
else
{
SPWeb web = SPContext.Current.Web;
web.AllowUnsafeUpdates = true;
SPQuery query = new SPQuery();
query.Query = "" + "" + "method1" + "" + "" + "method3" + "" + "" + "method2" + "";
//query.Query = "" + "" + "method3" + "";
SPView view = web.Lists["List name on which you want to do filteration"].Views["All Items"];
view.Query = query.Query;
view.Update();


if (Page.Session["User"] == null)
{
Page.Session["User"] = currentUser.LoginName.ToString();
// string script = "";
// Page.RegisterStartupScript("Refresh", script);


}
else if (Page.Session["User"].ToString() != currentUser.LoginName.ToString())
{
Page.Session["User"] = currentUser.LoginName.ToString();
// string script = "";
// Page.RegisterStartupScript("test", script);
}


}//currentUser.IsSiteAdmin
}//RunWithElevatedPrivileges
); //delegate ends
}//Render
}//class
}//namespace

Posted by Vaibhav Jain (Success is always one step ahead)

Item Level Security : Document Library Limitations : WSS Custom Event

After long time i came to know that item level security is not supported on document library as it is supported only on custom sharepoint list: refer below link to implement item level security on document library :
My project requirement was: Current logged in user can view all documents but delete only its own document and i have done it thru below programming for event handler where i have changed some of code as per my requirement.

Step 1: We will start by opening our Microsoft Visual Studio 2005 and create a new SharePoint Empty Project.

Step 2:Subsequently, we will add an Event Receiver item to our project. To do this right-click the project in the Solution Explorer > Add > New Item. In the Add new Item dialog box, select Event Receiver, name it CustomEvent, and then click Add. A Create Event Receiver dialog box will be displayed.

Stpe 3:Since we will customize a Document Library, select Document Library from the drop-down list in the Create Event Receiver dialog box, and then click Add. A CustomEvent folder with ItemEventReceiver.cs, ItemEventReceiver.xml, ListEventReceiver.cs, and ListEventReceiver.xml files will automatically be added to our project.

Step 4: Now it is time for us to write few lines of code. Let us open the ItemEventReceiver.cs file. Uncomment the ItemDeleting event, and then write the code below:
public override void ItemDeleting(SPItemEventProperties properties)
{
if (properties.ListTitle == "Custom Events")
{
properties.ErrorMessage = "For demonstration purposes, deleting is not allowed.";
properties.Cancel = true;
}
}

Step 5: To automate the deployment process, let us set the Start Action of our project. To do this, click Project > Project Name Properties. In the Project Properties page, select Debug tab. And in the Start Action section, select Start Browser with URL option, and then write http://sharepointking/

Step 6: Finally, let us build and deploy our project. To do this, click Build > Debug Project Name. If successful, click Build > Deploy Project Name.

Step 7: Upon successful deployment, let us open our SharePoint Web application, navigate to our Custom Events Document Library, add a document, then attempt to delete such document, and you would expect retention of the document with an error message

Posted by Vaibhav Jain (Success is always one step ahead)

Windows SharePoint Services

Windows SharePoint Services (WSS) is the basic part of Microsoft SharePoint, offering collaboration and document management functionality. It also includes a collection of web parts, that can be embedded into web pages to provide a certain functionality. SharePoint includes web parts such as workspaces and dashboards, navigation tools, lists, alerts (including e-mail alerts), shared calendar, contact lists, wikis and discussion boards. It can be configured to return separate content for Intranet, Extranet and Internet locations.

Built on Windows Server 2003, Windows SharePoint Services also gives organizations a cost-effective foundation platform for building Web-based business applications that can scale easily to meet the changing and growing needs of business. Robust administrative controls for managing storage and Web infrastructure give IT departments a cost-effective way to implement and manage a high-performance collaboration environment. The Windows Server 2008 architecture extends these values further by providing significant enhancements in manageability, security, and reliability.

You can download this FREE book of Development Projects with Windows SharePoint Services