Flexgrid error tooltips remain viewable after validating table data

Flexgrid error tooltips remain viewable after validating table data

Posted by: peter_murray on 29 September 2021, 4:04 pm EST

• 

  peter_murray

  • Post Options:
  • Link
    Copy

  Posted 29 September 2021, 4:04 pm EST - Updated 3 October 2022, 12:28 pm EST

  We’ve been running into a problem where our flexgrid tables, after validating their data on both our client and server side code, retains an error tooltip even though there is no error present in that row.

  Specifically, what happens is we highlight two rows as in error if they contain duplicate data. When one of the duplicate rows is deleted, our server code deletes the selected row, validates that the remaining rows are not in error, and returns those remaining rows to the client, which does some validation of its own. At this point, visually, there are no errors in the table, however if a user hovers their mouse over the row header of the duplicate row that wasn’t deleted, an error tooltip will show despite there being no indication of an error in that row.

  Stepping through breakpoints in the code reveals nothing is wrong with the client or server side validation. Both determine that there is no error with the remaining row since the duplicate was deleted, and the data they return adds nothing that would also add an additional tooltip to the table. Our flexgrid object in this component has no error data attached to this row or cell, nor does its html have the wj-state-invalid class attached to it. It just, for whatever reason, fails to remove one of the tooltips. Any suggestions as to how we might fix this would be appreciated.

  We’re using version 5.20211.794 of wijmo, as well.

  

  747×232 6.01 KB

• 

  sonu.pandey

  

  • Post Options:
  • Link
    Copy

  Posted 30 September 2021, 9:03 am EST

  Hello,

  We appologize, but we are unable to replicate the issue at our end, Could you please provide a sample replicating the issue, it is possible that the issue is arising due to some code specific to your application. However, you may try few suggestions that might work for you:

  1. Commit the changes after updating the grid by calling commitEdit() method of CollectionView or refreshing the collectionView as the getError determines whether a specific property of an item contains validation errors so it might be possible that the items are not updated yet.

  2. If the above point is satisfied, please make sure to invalidate the FlexGrid to update the changes reflected after the new data is introduced into the grid.

  Since we are unable to replicate the issue, I would request you to share a sample that demonstrates the issue so that we could further investigate the root cause of the issue and assist you accordingly. Without a sample to replicate the issue, we cannot comment on the actual nature of the issue.

  Regards