Wijmo cell validation with getError function after 5.20193.646

Posted by: meera.wisniewski on 17 June 2021, 3:45 pm EST

    • Post Options:
    • Link

    Posted 17 June 2021, 3:45 pm EST - Updated 3 October 2022, 1:36 pm EST

    Hello,
    

    I have validation in a wijmo flexgrid tied into the getError function on the collection view. It seems like the grid isn’t letting me add values in the combobox. On the cell edit ending event, the grid is locked down. I am unable to select anything else in the grid, and the combobox cell tells me to enter a name with a “wj-state-invalid” on the css. If I select other values from the combo box it is still invalid. However, the combo boxes that are existing and populated can be changed, so this issue appears to be specifically for empty combo boxes.

    It appears as if my get error function runs, and then also the wijmo default get error function is running, in addition, to set errors. I had manually overridden the errors to be removed and flags false, while returning null as to prevent any errors. Meanwhile, the errors still claiming my combo box input is invalid. Is this just an issue with after 5.20193.646? I am trying to determine if future versions have a fix for this?

    Thanks!

  • Posted 17 June 2021, 3:50 pm EST - Updated 3 October 2022, 1:36 pm EST

  • Posted 21 June 2021, 6:23 am EST

    Hi Meera,

    We are not able to replicate the issue with the given information, can you please elaborate more on the following points:

    1. Are we using EventBased Validation (through cell edit ended) along with the getError method of collectionView?
    2. What are the criteria for the validation which is being performed?
    3. Does the above issue arise when we try to add new rows or does it replicates in any other scenario as well?

    If possible, kindly provide a sample depicting the above issues or make changes in the below sample, so that we could debug it and reply accordingly.

    Sample for reference: https://stackblitz.com/edit/angular-csap3n

    As a suggestion, you can use the validateEdits property of FlexGrid. Try setting its value to false and check if the issue persists.

    https://www.grapecity.com/wijmo/api/classes/wijmo_grid.flexgrid.html#validateedits

    Regards,

    Ashwin

  • Posted 21 June 2021, 1:20 pm EST

    This issue appears to have been solved by adding validate-edits=“false”. The custom validation is then able to run without interference from the package’s validate edits.

    Thank you for your reply

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels