For example, you can subscribe to the "Item Added" event for a specific list, and have your custom code execute when the event fires.
Also, you are in SP 2007 able to cancel an event if you have the need for it, hence providing the user with an error message in the browser.
So – now that we’ve got a As you can see, your custom HTML now appears.
Apparently I didn’t do any fancy design on my Application Page, but you can add more images and whatever else you want to make it more easy for the users to understand what actually went wrong – and how to make it on from there.
This is true for Share Point 2010 and Share Point 2013 and its present only for custom lists but not for document libraries.
I’ve done some testing and the results are presented in this post. The test is performed when adding/changing/deleting the item’s user field using the UI (New and Edit form) and when adding/changing/deleting the field pragmatically.
In the tests user1 and user2 are used and they happen to have ID of 41 and 42.
When adding, modifying and deleting item using the UI: You can see that the problem is only with claims based authentication while with classic authentication the results are the same when the item is added/modified using the UI and when it’s added/modified programmatically.
The difference is present in After Properties of Item Adding and Item Updating event.Below are shown the results only for the events that have this problem.At the end of this post you can find the complete test results for Share Point 2013.So, in this article I will walk you through the news with Event Receivers in SP 2010 in regards to creating custom Error Pages for your users.Using Visual Studio 2010, choose the new template called "Event Receiver" like so: Choose if you want this to be a Farm Solution or a Sandboxed Solution.
You’re presented with the following project structure that is created for us: I will not dig deep on how and why the structure of the project looks the way it does now – it will be covered in another article.