Event Handler, SharePoint 2010, SharePoint 2013

Whats new in SharePoint 2013 Event Receivers

SharePoint 2013 has Introduced a New and much needed Event Receiver class “SPSecurityEventReceiver”. Using this class you can add Event Handlers around SharePoint Groups, Users, Roles and Permission Inheritance.

Here is the list of events that you can handle in SharePoint 2013 Preview.

You can Handle the following SharePoint Group Events

  • GroupAdded
  • GroupAdding
  • GroupDeleted
  • GroupDeleting
  • GroupUpdated
  • GroupUpdating


You can Handle the following SharePoint User Events

  • GroupUserAdded
  • GroupUserAdding
  • GroupUserDeleted
  • GroupUserDeleting
  • RoleAssignmentAdded
  • RoleAssignmentAdding
  • RoleAssignmentDeleted
  • RoleAssignmentDeleting
  • RoleDefinitionAdded
  • RoleDefinitionAdding
  • RoleDefinitionDeleted
  • RoleDefinitionDeleting
  • RoleDefinitionUpdated
  • RoleDefinitionUpdating


You can Handle the following Inheritance Events

  • InheritanceBreaking
  • InheritanceBroken
  • InheritanceReset
  • InheritanceResetting
SharePoint 2010

SharePoint 2001, 2003, 2007, 2010, 2013… 2016 !

Adding SharePoint 2001, Joel Oleson had commented on FB to “don’t forget 2001” and Guillaume Meyer also commented on this post with a link to a picture of SharePoint 2001 that I will use here.

And how it used to look like:

SharePoint 2003

And how it used to look like:


SharePoint 2007

And how it used to look like:


SharePoint 2010

And how it used to look like:

SharePoint 2013

And how it used to look like:


SharePoint 2016



SharePoint 2010

SharePoint (and Project Server) Shenanigans

On one of my current projects I have had cause to ensure that no special characters are in the Title field of a SharePoint 2010 list form.

This is because we are using the Title field as the Plan Name in a Project Create process in Project Server 2010.  As a result we need to ensure that the Event Handler we are creating has validated data that the PS2010 PSI Web Service can accept for the Plan Name.

I created the following script to validate the data being entered into the Title field of the list form as it is being entered.

I manipulate the Save Buttons in the ribbon and the list form to ensure that the user cannot enter invalid data into the form.

To ensure a good user experience, I add an extra <DIV> element next to the Title field to notify the user of what is…

View original post 294 more words

SharePoint 2010

Pradip's Blog

Validation in SharePoint 2010

Most of the developers faced issues with column validations in SharePoint 2003/2007. It is really painful to write the validation using custom approach like JavaScript or jQuery (I don’t know how to do this one :().  SharePoint 2010 provides the following validations in Out of the Box. Items cannot be saved until these validation criteria are met and custom messages, which can be set for specific validation failure cases, are displayed to the user.

  • Column Level Validation
  • List Level Validation

1. Column Level Validation

We are already familiar with some sort of validation in column level; Date and Time field doesn’t allow us to input general text; Number doesn’t allow us to input text value, moreover, we can set range of the valid values (Max, Min).

Somewhat similar, Column Validation is the new feature of SharePoint 2010 which allows user to validate the input against the…

View original post 1,139 more words

SharePoint 2010

I will add later a way to this more dynamically

Nick Hurst's Blog

There are two easy ways that I know of to get a list GUID.  One way to get the GUID is through the url of some of the list settings:

  • Go to List Settings
  • Click on one of the bottom links in either the General Settings or Permissions and Management categories (Rating settings, Audience targeting settings, Generate file plan report, Information management policy settings, etc)
  • Grab the GUID out of the url of that page (http://sitename/_layouts/MetaNavSettings.aspx?List={b569deaa-ea4a-4655-b6ad-6aa47fada6d8}

The other easy way is to open up that list in SharePoint Designer, when you click on a list there will be a panel called “List Information”.  In this panel the GUID is displayed next to the “List ID:” heading.

View original post

SharePoint 2010

Sandboxed Solutions are deprecated in SharePoint 2013

Microsoft in 16 July 2012 published many articles on MSDN, and said that Sandboxed Solutions are deprecated in SharePoint 2013, I really wanted to post about it but thought I should wait for sometime..

Till I found Andrew Connell post http://www.andrewconnell.com/blog/archive/2012/07/16/understanding-sharepoint-2013-apps-aka-apps-101.aspx and in the comments as I was reading, I realized that it was good to wait as Microsoft changes lots of things from Consumer Preview edition to Beta 1 to Beta 2 if there will be 2 to RTM and so on…

But there is no bug because it is really deprecated.

Then another post from elumenotion Blog http://www.elumenotion.com/Blog/Lists/Posts/Post.aspx?ID=158 thay says:

Microsoft is deprecating Sandboxed Solutions in SharePoint 2013

This means that the functionality will still be available for use in SharePoint 2013, but primarily for backwards compatibility with existing solutions built using the sandbox solution approach.

Microsoft’s guidance is that if you are building new applications that in the past you would have deployed as sandbox solutions, you should use the new App model for those solutions instead of using sandbox solutions.

They took a similar approach in SharePoint 2010 with the STSADM command line administration tool when it was deprecated in favor of the SharePoint 2010 Management Shell and the numerous PowerShell cmdlets deployed with that tool. STSADM is still available in SharePoint 2010, but mainly just to allow for older scripts and tools that use STSADM to still function with SharePoint 2010.