I have noticed an “editable” grid peculiarity. In the “MM Northwind Sample Application_CSharp” there is a validation rule set up on the “OrderDetail.Discount” column. This rule checks for a none empty value, in the case of a numeric field a none zero amount. To illustrate the problem run the application. Position to a customer order that has multiple order detail lines in the order detail grid and change the discount column in the first row to 0. Press the “Save” button in the Order Header section of the screen to trigger an “AutoSaveOnParentSaved”. A data entry error occurs and a red dot is placed next to the “discount” value in the grid that is in error. This is what I would expect. Now replace the “discount” amount in the first row with a valid amount (1) and place a 0 in the second rows discount amount. Press the “Save” button in the Order Header section of the screen. The invalid amount is accepted in the second row of the grid and form control is return to the “List” page indicating all is well when in fact it really isn’t.

I have an “editable” grid in my app that is working in a similar fashion. Is this normal behavior? Should I not be using editable grids?