The detailsview fired event itemupdating which
Is Post Back is always true when the Init for the Details View is called.How can I distinguish the initial load from subsequent ones? If the data binding does not happen again, does the server just keep loading the data for subsequent postbacks from View State? The Mode Changing and Init events fire because they specify a Handles clause.This was the only way I got things to worked for me.The Item Updated event never fired but I got the Details View to works how I wanted. If it's bound via Linq Data Source, Sql Data Source or Object Data Source I suggest you have a look at the Updating Event.There you have access to the object via the Event Args. New Object or something like that You can cast this property into the corresponding type and make your changes.
The edit button required two clicks to change the mode to Edit instead of Read Only.
In this section, we’ll learn about the events raised by these controls.
We’ll focus on the events that relate to editing and updating data, as our next goal will be to allow users to edit employee details in the buttons.
I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.
We may never know about all of the dangers lurking out there, but today we’re going to cover at least one danger you may encounter while writing event receivers – an annoying issue with the Item Updating and Item Updated events firing twice.