Hi,
Our users use the "Paste into XamDataGrid" feature rather extensively. A specific portion of the Paste functionality stopped working when we recently upgraded to NetAdvantage for Win Client 2010 Vol. 2. We have also installed the latest service release (NetAdvantage_WPFAndDV_20102.2001_SR) and still no success.
Please see the explanation below of exactly what Paste feature I am referring to:
We use the XamComboEditor control extensively in our XamdataGrids. It would seem, that since recently, when a XamComboEditor is bound to a complex type, that the XamComboEditor is unable to resolve a matching item when pasting a text value that should match the displaymember text of one of its items.
If you copy a cell's value in the grid, and then paste into the same cell in another row, IT WORKS FINE,
BUT when you paste a TEXT value (that should match the displaymember text of 1 of its items) the grid raise the following error:
---------------------------Paste Error---------------------------An error occurred while validating the value for the cell. Additional information:Continue with the remaining cells?---------------------------OK Cancel ---------------------------
If I however Paste a TEXT value that matches one of the items' ValueMembers (ID value...), it does resolve the correct item.
Please use the attached sample application provided and follow the steps below.
PS I created the sample app using some of the sample code from the latest feature browser incorporating 2 separate implementations of the XamComboEditor.
.
I don't know if this is an issue with the XamComboEditor or the ClipboardPasting code-behind of the XamDataGrid, but my primary concern is that this used to work, but since upgrading it does not work anymore.
I would really appreciate a response as this has raised some eyebrows from our users.
Regards,
Martin
Anyone??
Hello Martin,
If this is reproducible in an older version, then it is probably a regression issue. However, I was not able to reproduce this with 10.1. The behavior is the same as the 10.2 version. I have tested this with 10.1.20101.2018 build. Which build were you using before the upgrade?