Looking at the deliver1.PNG, there is a grid with a 'MultiColumnComboBox' component inside one of the columns. When a name is removed from a role in one row (deliver2.PNG), then that row is deleted/removed, the row below it moves up but loses its name on the UI but the data is not effected (deliver3.PNG).
Can confirm all data is intact when passing information to the 'MultiColumnComboBox' component, it's just a UI bug which doesn't display the value that was selected in the unedited/deleted row. Can also confirm this bug exists in other grids with 'MultiColumnComboBox' components.
The code path is as follows in images code1.PNG, code2.PNG, and code3.PNG. It can be seen there is a UserComboBoxCell element which returns a component called 'EditableGridMultiColumnComboBoxCell'. It is this component that uses the the 'MultiColumnComboBox' component.
Hello, Jake,
We created a working example for your use case but the issue does not reproduce on our end.
Please review the following link where you can see the example we used for testing. Please check the example and see if we missed something compared to the real application.
If the issue still occurs, please modify the example to replicate the same case and we will be happy to take a look.
Regards, Philip Progress Telerik
Hello Filip, thanks for getting back so fast. As you suggested we do have the dataItemKey="id" currently in place. I have seen what this value is and it appears to be the grid id value (ie. '_0-1_cell', etc). So I can see this as an issue when a row is deleted, the new row assumes the deleted row's id and it appears nothing changed for rendering.
To test this out further, I did make a change so that this id was unique, but it still replicated the same error.
What version does dataItemKey need? We are currently at 4.5.0 with kendo-react-dropdowns.
Hеllo, Jake,
The UI issue that you are experiencing could be fixed by setting the dataitemKey property to id. That will allow the UI to clear the entire row in case the id is different because by default this is done by index and it doesn't change in your case. Please bear in mind that this prop is relatively new and if you use an older version you may have to update it, otherwise, you won't have access to it.
Regards, Philip Progress Telerik