This can be useful, if you would like to invoke specific audit method or call custom methods to populate dependent transient VO's with updated data.
To enable such triggers, you must add a listener for VO, this can be done during VO creation from standard create method: ADF BC API methods, such as row Inserted, row Updated, row Deleted can be overridden.
This works as expected and I can put a breakpoint in the Row Command event handler to see the "Event" command name.
After it has been clicked the postback places that row in edit mode. At this point in time the above Edit Item Template is displayed with two Image Buttons within it.
The Grid View 'Grid View1' fired event Sorting which wasn't handled.
So when we use these special key words as the Command Name for the buttons in the Grid View, they automatically invoke the built in functionality of the Grid View when we click on the button.
The Grid View does know the events that should be used to implement them, so the exceptions shown above are thrown when you try to perform one of these operations, but you have implemented the appropriate event handler.
The example shown here is for a Grid View, but the same types of event handlers must be implemented in roughly the same way for other data controls including the Form View, Details View, and List View. This is the final Grid View markup, so you can see the event handlers we’re going to implement.
event is raised when a row's Edit button is clicked, but before the Grid View control enters edit mode.
This enables you to provide an event-handling method that performs a custom routine, such as canceling the edit operation, whenever this event occurs.