Fired event itemupdating which wasn t handled
The Grid View 'Grid View1' fired event Sorting which wasn't handled.The Grid View 'Grid View1' fired event Row Deleting which wasn't handled. When I say manually databinding I mean not using a data source control specified as a Data Source ID, but rather setting the Grid View’s Data Source equal to the appropriate data object and calling Data Bind. NET 2.0 are familiar with how to deal with this, but since ASP.So the alternative is to check the field value first before making any changes to avoid the update operation recurrence. forum=sharepointdevelopment Moreover, a better programming practice is to check the type of event first: Thank you for your answer Nadeem.I use item Updated event to write some stuff to a word document in the document library list, in my sample code i have updated item "Title" just for testing purposes i have updated my question accordingly.I had already covered all the basic things such as: I even went as far as completely emptying the body of the handler to see that in fact the event was firing twice.As with any problem, I always try to resolve it through the process of elimination by first isolating the core issue into a test project and therefore out of the primary project I’m experiencing it in because sometimes you can’t see the forest because of the trees. After creating the simple project, the problem was still there. The event wasn’t firing twice for the same list, it was firing for ALL Lists. I took another look at my event receiver I had added via Visual Studio to the project. Yes, I had left the file for the Event Receiver there, and therefore when the feature was activated for the project, the receiver got associated to ALL lists on the site.Even a simple app to enumerate the event receivers associated to the list only showed the one instance. Well, I had moved on to other things again, when all of a sudden, I noticed that new tasks were being created in the task list for some documents that I was uploading to a different document library. That’s pretty much the symptom for a receiver associated to a list template, but this was NOT a list template! It wasn’t going to show up in the Event Receivers collection for that list instance, because it was associated to the list type.When I added it to the list instance, it just caused the event to fire twice on THAT list.
In this example, we’ll go through a fully featured Grid View with editing, deleting, selecting, sorting, and paging functionality that is manually bound and identify the limitations and some of the workarounds. Sql Data Source, Object Data Source, Linq Data Source, etc) specified in a Data Source ID, the Grid View can automate many functions because, through the data source control, the Grid View on its own can perform the following operations: When you manually bind data to a Grid View, the Grid View itself cannot perform these operations, so they must be implemented in your code.And about your better programming practice comment...my Remote Event Receiver is registered on the list in App Installed event with Event Receiver Definition Creation Information Event Type set to Item Updated so it fires only when item is updated so i don't think that better programming practice is to check something that is always true Process One Way Event is called for all "ed" events.If you have other ways of editing this property, like through CSOM, then you can have your other code set this to false and your event reciever set this to true.Then you can check if it exists, and if so, is it set to true.