Advanced Forum Search Results
-
Thanks for the kind words Colin. :-)
Yes, this is a known bug that has been discussed on a bunch of threads on the forums. DomainDataSource was incorrectly resurrecting entities after they were deleted and you called SubmitChanges. It's an unfortunate bug that I wish I hadn't missed in the July release (we found it only a couple of ...
-
The entire list would get serialized and sent to the client again. It's a stateless load operation, the merge happens on the client.
-
Try handling the DomainDataSource.LoadingData event. The event args for that event includes a MergeOption property. By default, DomainDataSource uses the KeepCurrentValues option, but you can change it to OverwriteCurrentValues to achieve what you're expecting.
-
You'll want to apply the PageSize property to the DomainDataSource (recommended over specifying it on the DataPager). If your domain service method is an IQueryable, then the Skip/Take expressions will get passed all the way to your server query. If your domain service method is an IEnumerable however, then your server query will ...
-
I've put together a way to get around this problem of binding the DataForm directly to the EntityList. I blogged about it here:
http://jeffhandley.com/archive/2009/08/14/entitycollectionviewconverter.aspx
You'll notice that I'm using the name EntityCollectionView for the solution, but please don't confuse this with the ...
-
DomainDataSource translates LoadSize and PageSize/PageIndex into Skip and Take expressions on the EntityQuery<T>. This in turn gets applied to your IQueryable<T> in your DomainService.
For instance, with a PageSize of 3 and a LoadSize of 12, for the initial load, that gets translated into a Take(12). Then, when you go to ...
-
This looks like a bug with the ControlParameter. I've filed the bug and we'll dig into it.
Thanks,
Jeff Handley
-
I've recently learn that you can do the following:
<dds:DomainDataSource x:Name="ContactSource" PageSize="10" QueryName="GetContacts">
...
-
I'm terribly sorry that this bug is causing you trouble. It was the assumption that the Entity would be Deleted that led to the bug, as you found. However, the Entity's state becomes New, also as you said.
When changes are submitted, where an Entity is deleted, that actual Entity object becomes New, as if you were to re-attach ...
-
Sorry, but this is a bug that doesn't have a workaround in the July 2009 Preview release.