Won't Fix
Last Updated: 14 Sep 2020 12:16 by ADMIN
ADMIN
Stefan
Created on: 17 Aug 2018 14:42
Category: GridView
Type: Bug Report
2
GridView: When validating through IDataErrorInfo the tooltip errors are updated only after trying to commit a row edit

		
11 comments
ADMIN
Ivan Petrov
Posted on: 14 Sep 2020 11:32

Hello all,

The behavior of RadGridView is correct in this case. You can read a further clarification below.

RadGridView has row-level and cell-level validation mechanisms. In the case of IDataErrorInfo validation, these are corresponding to the Error and string indexer properties of the interface. These are two separate entities meant for different purposes. You can have valid cell values but the combination of these cell values may result in an invalid row data. Here's an example: two cells, representing a percentage of the same entity, that have each a value of 60%. Individually they have valid values (0-100%) but the sum of 120% is not valid for the row (entity). When either of the properties in the IDataErrorInfo has values it will be displayed in the grid UI. The developer is responsible for the management of the error state for both cell(s) and row in the corresponding ViewModel.

Regards,
Ivan Petrov
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

ADMIN
Dinko
Posted on: 05 May 2020 05:59

Hello Rashmi,

This behavior is still not planned for fixing. I completely understand that this behavior is causing you trouble, but it will require a major refactoring in the core logic of RadGridView's validating mechanism. I am afraid our roadmap is full for the near future, so this task still resides in our backlog.

Regards,
Dinko
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Rashmi
Posted on: 29 Apr 2020 04:36

Please let us know if there is any update on this issue?

 

ADMIN
Vera
Posted on: 22 Nov 2019 15:18

Hi Rashmi,

 

We tried to solve the problem but the fix actually caused some new ones and we had to revert it. This is why the status of this item is Approved. I cannot commit to any specific date or release where this issue will be fixed as its source is in the core logic of RadGridView's validating mechanism.

Please excuse us for the inconvenience caused.

 

Regards,
Vera
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Rashmi
Posted on: 20 Nov 2019 10:50

We tested this issue on 'Telerik UI for WPF latest version 2019.3.1023.45' and found that this issue is still not fixed.

Please let us know the expected resolution time for this issue. 

ADMIN
Vera
Posted on: 11 Oct 2018 12:09
The fix for this issue will be available with 2018 R3 SP expected in the middle of October.
Rashmi
Posted on: 21 Aug 2018 05:47
Hi Telerik Team,

Validation messages on error tooltip should get refreshed not only when row is in edit mode but also when the underlying datacontext is changed through the code.
That means any change on a property that grid binds to should also trigger refresh of IDataErrorInfo errors on UI.

Please fix this soon.

Thanks,
Rashmi Singh
Abhishek
Posted on: 21 Aug 2018 05:34
Hi team,
This is not a correct behavior please fix this issue.
Mahendra
Posted on: 21 Aug 2018 05:27
Yes this fix is required. It should be fix as soon as possible.
chandramohan
Posted on: 21 Aug 2018 05:26
Yes, Errors property implementation behavior should be correct and hence please fix this.
Prateek
Posted on: 20 Aug 2018 15:37
There are issues around IDataErrorInfo. We commented the code for 'Errors' property implementation and returned 'null' to avoid multiple messages. This is not a correct behavior.