Hello Telerik team,
we updated silverlight project from Telerik version Q3 2010 SP1 to Telerik version Q1 2013 SP1.
We use RowValidation and validate the errors in the handling method RowValidating(object sender, GridViewRowValidatingEventArgs e).
If a row contains errors (multiple cells in one row are validated) - the e.IsValid flag will be set to false, and the e.ValidationResults gets the list with GridViewCellValidationResults. The row is marked with red background color, and in the tooltips all error messages are shown.
If then correct values are set in the marked row, in the RowValidating method the e.IsValid gets true, and the RowValidated Method will be called, too. But in the view the row is still marked in red.
By debugging we found out, that although in the RowValidating method the e.IsValid has the value true, the e.row.IsValid has still the value false and e.row.Errors keeps the list with errors.
The described problem did not occur with version Q3 2010 SP1.
What should we do to get the row vaidation working correctly again?
(We would prefer to still have the validation in the RowValidation method.)
Kind regards,
Li
we updated silverlight project from Telerik version Q3 2010 SP1 to Telerik version Q1 2013 SP1.
We use RowValidation and validate the errors in the handling method RowValidating(object sender, GridViewRowValidatingEventArgs e).
If a row contains errors (multiple cells in one row are validated) - the e.IsValid flag will be set to false, and the e.ValidationResults gets the list with GridViewCellValidationResults. The row is marked with red background color, and in the tooltips all error messages are shown.
If then correct values are set in the marked row, in the RowValidating method the e.IsValid gets true, and the RowValidated Method will be called, too. But in the view the row is still marked in red.
By debugging we found out, that although in the RowValidating method the e.IsValid has the value true, the e.row.IsValid has still the value false and e.row.Errors keeps the list with errors.
The described problem did not occur with version Q3 2010 SP1.
What should we do to get the row vaidation working correctly again?
(We would prefer to still have the validation in the RowValidation method.)
Kind regards,
Li