I often get asked, "Why isn't it easier to access the modification state of a row on the client?"
I've blogged about this topic before and explained why in general the status of a view row is not well-defined. In short, since a view object row can include data from multiple entity objects, some of which might be NEW while others are UNMODIFIED, the status of the overall view row might not be well-defined.
However, for view objects where there is a single updateable entity object, the row status can reasonable be defined simply as the row status of the underlying entity object.
I've added example #46 (Exposing Entity Row State as View Row State on the Client in a Generic Way) to my page of not yet documented examples that illustrates a generic technique to expose a dynamic "RowState" attribute on any view object whose value exposes the underlying primary entity object's row state.
3:06:30 PM 
|
