Hi
I have a screen in Silverlight which is comprised of a header record, and then a datagrid which might contain up to 1000 records.
The user doesn't want to use paging and would prefer to just scroll down the list of records in the datagrid and enter a value in one of the cells for what could be just a handful of records.
When the user clicks Save the entire object is transported back to the server, including the 1000 odd records. This is resulting in some poor performance (even with compression).
Is there any technique you might suggest to handle this kind of suggestion?
The question is being asked..."why are we transporting back every record if we're only editing three?".
Thanks
Damien