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?
Martin,
What I meant is that I managed to reproduce the behavior you are describing (the error) in both 10.1 and 10.2 (with the latest service releases for both versions). I am going to test this with 10.1 (1002).
Thanx Alex,
Awaiting your response.
I have tested this with 9.2, 10.1 and 10.2 release versions against .NetFramework 3.0, 3.5 and 4.0 under Windows 7 and XP. All with the same result. I could not find a version that this was working correctly with. However, this is still an issue with this functionality and we will look into this. I have created a support case on your behalf for this (CAS-50250-BX49BY) so that you can be notified when this is resolved and the service release is out.
Hi Alex,
Thank you for all your efforts. Your response exceeded my expectations!
I will inform our support division and will look out for the next service release.
PS: How will I know if this issue was resolved in a future service release? Will I be notified or will I have to look at the release notes?
Thanx again!
Thumbs Up!
Shortly you will receive an email notification from the support case on the email address(connected to your user account). Through this case you will be notified when a resolution for this issue is reached and the service release is out and ready to download. The status of your support cases you can follow from this page.
Fixed in the latest service release 10.3 1296
Thans guys/girls
Hello,
The issue is still in development (reference number 36390). I will create a support case on your behalf and associate it with this issue, so that you can be notified when this is resolved.
I have run into the same issue. Was there a resolution or do I need to open up a new ticket.