Here is what I’m trying to do:
I've got a classic form with two grids; say a left grid and a right grid. The left contains all the items of a collection and the right one, a subset of the left, all items with a specific property set to true. Between these two grids are buttons that "move" items from the left to the right and vice versa.
Now, these items come from a TypedList as I want to be able to see simultaneously all the related fields of each entity in one row. When I press the "move" button, for each selected row of the left grid I instantiate a new entity, set the IsNew property to true, set the property in question to true and I save the entity (option 2 on "Modifying an entity" - Adapter). Then, I re-fetch the typed list and the items appear on the right grid.
So, my concerns are: Is this the optimal way of doing all that? Is there a way to not use a TypedList, as it is not updatable? To overcome this, I have to update the datastore in order to see the changes. That means that I can’t implement an OK, Cancel form logic. If for example the typed list was updatable, I would have been able to make all the changes in memory and then commit them or discard them with the OK and Cancel buttons.
Thanx,
Manos