SharePoint 2010 Developer Dashboard Visualizer

SharePoint 2010 Developer Dashboard Visualizer is a jQuery-based solution that extends the Developer Dashboard by plotting an interactive diagram with data from the Developer Dashboard, giving you an **instant** insight into where the bottlenecks are in your code.

Get SharePoint 2010 Developer Dashboard Visualizer from here and let me know what you think!

Reusable and Globally Reusable Workflows in SharePoint 2010

“SharePoint Designer Workflows” is nothing new, we’ve had that in 2007 as well. In SPD 2007, workflows were not reusable. Once you have defined a workflow, you cannot move that workflow to another list or reuse it somewhere else.

NOW in SharePoint 2010, this is possible! You can create reusable workflows and attach them to more than one list.

“Reusable workflows” is one of the coolest features in SharePoint 2010, however when I opened up SPD for the first time, I was a bit confused because I noticed two different terms “Reusable Workflows” and ‘Globally Reusable Workflows”.



When you create a Reusable workflow in SharePoint Designer 2010, it’s by default reusable within the site it has been created in, which means that it can be attached to any list within this site. But what if you want your workflow to be reusable in the whole site collection ? Well, this is the definition of “Globally Reusable Workflows”. You can easily convert your workflows to be available anywhere in your site collection by opening your workflow and clicking on “Convert to Globally Reusable” from the ribbon as shown below.





Also it’s worth mentioning that only the workflows created at the root level of the site collection can be converted to be Globally Reusable but other ones created in sub sites cannot. Try to create a workflow in a sub site , open it and note that the Conversion button is dimmed.



Another important question is what if I want to take my workflow and give it to somebody else in a different site collection? There’s another button in the ribbon called “Save as Template”, this takes the workflow, put it in a wsp file and save it to the ‘Site Assets” library. You can export this file and deploy it to other site collection and what’s really cool is that you can import this wsp into Visual Studio and extend it over there. Very cool stuff! Thanks Microsoft for this  feature!




Speaking at SharePoint Techday [December, 5th]

Egypt SharePoint User Group is pleased to announce its co-operation with DotNetWork User Group in putting together a full day about SharePoint 2010.



TechDays is a new type of .network’s gatherings. It consists of 2+ sessions talking about a specific technology from the basic to advanced levels going in sequence to expose audience to different areas of that technology.

I’m pleased to be presenting there with Marwan Tarek and Mohamed Yehia, please find below the event details :

Date: Saturday, December 5th 2009
Time: 10:30 AM – 4:00 PM
Place: Dar El Deyafa – Ain Shams University – Isis Hall – first floor, El khaleefa el Mamoon – EL Abbasia– Cairo
10:30 AM – 12:00 PM SharePoint 2010, Getting Ready! Marwan Tarek
12:30 PM – 02:00 PM Developers’ tools for SharePoint 2010 Mohamed Yehia
02:30 PM – 04:00 PM Creating No-Code SharePoint Designer Solutions for SharePoint2010 Ayman ElHattab
The ticket to attend the event is 15 L.E.

Hope to see you all there!

Jordan SharePoint User Group – Nov 2009 Meeting

Jordan SharePoint User Group has recently conducted November 2009 meeting on Wednesday, November 11, 2009 at Princess Sumaya University for Technology.

21 22


Mohamed Saleh [C# MVP] and Ali Nimer, Sr. SharePoint Developers delivered exciting sessions covering how to build browser-enabled web forms using Microsoft InfoPath Forms Services

Here are some of the covered topics:

· What is InfoPath and how does it work
· How to get InfoPath to work with SharePoint InfoPath Forms Services
· InfoPath or ASP.NET Web Forms?
· Consuming Web Services from InfoPath Forms
· Business Rules Verification and Validations

About JSUG :

The Jordan SharePoint User Group (JSUG) is the very first SharePoint User Group in the Middle East. It was formed to connect SharePoint professionals within Jordan together, to share knowledge and build a higher level of awareness for SharePoint Products and Technologies within the region.

Looking forward for more collaboration between JSUG and EGYSUG…

In SharePoint Designer 2010 : XSLT List View Web Part = List View Web Part + XSLT Data View Web Part

XSLT Data View Web Parts have been and still remain to be one of the most powerful web parts in SharePoint , some people call it “The Swiss Army Knife of SharePoint Web Parts” , the only problem that I can see with the Data View Web Part that once you add it to a web part page, the end users cannot further manipulate it, they have to come back to SPD Designer to modify it or directly edit the XSLT from the browser which is not an easy task (All data is retrieved as XML and manipulated using XSLT which is a very flexible way of transforming and presenting your data). Otherwise, the XSLT Data View Web Part is a wonderful web part, you can aggregate data from a variety of sources and present them in an awesome way.

In SharePoint 2007, we also had List View Web Part, which could be used to show a list content in a page but you cannot customize it that much in SPD 2007, you have to convert it to XSLT Data View Web part in order to customize or extend it.

In SPD 2010, there is a new web part called XSLT List View Web Part which is a combination of both :

XSLT List View Web Part = List View Web Part + XSLT Data View Web Part



You can customize it directly through SPD 2010 and once it’s added to a page, end users can still customize it using the browser by adding views and doing anything that was possible using List View Web Part.

Ah, by the way the Swiss Army Knife of SharePoint Web Parts still exists in SharePoint Designer 2010 with a much better designer surface using the new Ribbons interface 🙂


Creating mailing lists for SharePoint sites and blogs [No Code Required] – Part 6: Administering the mailing list using Microsoft Word Mail Merge

NOTE : This article was published on a couple of weeks ago and because of the wonderful feedback I received, I decided to cross-post it here too.


This is the sixth article in a multipart series that is intended to help you create mailing lists for your SharePoint sites or blogs without writing a single line of .NET Code. In the introductory article, I listed the project initiatives, requirements, and objectives. In Part 1, I created a secured backend where we will store the subscribers’ contacts. In Part 2, I configured the ‘Contact’ content type, created a subscription form for the mailing list and did some simple customizations to it. In Part 3, I utilized the thrilling DataFormWebPart to further extend and enhance the subscription form to meet the project requirements. In Part 4, I implemented requirement # 3 by creating a list that comprises the names of all the countries of the world and a lookup field that gets its values from this list. In Part 5, I showed you how to create the primary and secondary SharePoint Designer Workflows needed to meet our project requirements.

In the previous article, I showed you how to connect the approved contacts to Outlook by creating a workflow that is triggered when the list administrator approves a subscriber request moving their contact to the “Approved Subscribers” list. I have also provided you with some excellent resources if you need to know more about SharePoint Designer Workflows.

As I mentioned in Part 4, most of the questions that I have received lately focused on the sixth requirement. For easier reference, I have copied it below.

List administrators should be able to send e-mails to all the approved and registered users specifying some filters. For instance, the list administrator should be capable of sending e-mails to all the registered users from Canada”.

In this article, I will show you how to implement this requirement using Microsoft Word Mail Merge.

Unexpectedly, Microsoft Word has no option to pick a SharePoint list directly as the data source for a mail merge. However, we can work around this limitation by connecting our “Approved Subscribers” list to Outlook and selecting the Merge data source to be an Outlook Contacts List as shown in the following figures.












11 12 13 14 15







There you go! Yes, we are done; you can now create and administer your own mailing list for your SharePoint site or blog.

Since this series is intended to be educational, you should now be capable of:

  1. Creating and configuring SharePoint Lists using SharePoint Designer.
  2. Configuring anonymous contributions for SharePoint Lists.
  3. Creating simple SharePoint Designer workflows for sending confirmation mails to list subscribers.
  4. Configuring content approval for share point lists.
  5. Creating custom SharePoint list forms.
  6. Creating Client-Side validation for SharePoint list forms.
  7. Using the DataFormWebPart.
  8. Connecting SharePoint Lists to outlook.
  9. Using Word 2007 Mail Merge feature with SharePoint Lists.
  10. Using and creating SharePoint List Templates.
  11. Hiding SharePoint lists.
  12. Using lookup columns in SharePoint lists.

Again, I would like to thank everybody who took time to drop me an e-mail, follow me on twitter, or even leave me a comment. Your feedback, guys has always made my day.

So until I talk to you again (most probably about SharePoint 2010 ), check out my blog at , where you will find shorter articles, tips and tricks, questions and answers, and downloadable content. You can also follow me on Twitter  or drop me an e-mail at if you have any questions.

About EndUserSharePoint: is a community of SharePoint authors dedicated to providing content to SharePoint End Users on three levels: Information Worker, Power User/Site Administrator and Site Collection Administrator.