I have created a simple program to show that when changing a value in a cell, the value on another cell will be changed. This was working with no problem when I was using Version 2.8.0.When I upgraded to Version 2.9.0, the behavior changed.1) Change the value of cell#1, the value on cell#2 changes.2) Change the value of cell#1 back to the original value, the value on cell#2 does not change.
This was working correctly when using Version 2.8.0, when changing to original value in cell#1, the value in cell#2 also changes.
Does anyone have this same issue? Do you have any workaround to trigger the event no matter what the input value is?
Thank you in advance
Hello.
This was already reported internally and will be fixed on the next release under ROU-3950.The workaround might pass by overriding the method _cellEditHandler on the Grid Initialize event in order to remove the validation that checks the initial and new values.
This was introduced in version 2.9.0 to solve another issue on the dropdowns but we're trying to find a different approach.
Cheers,GM
I have attached here my oml (UserList screen)
It seems the widget has a bug.
When changing a value on a cell, it fires the event OnCellValueChange, and a changed flag is shown on UI. However, when the new changed value is matching with the original value, it clears the flag but this time, the event is not fired again because the value is same as old value.
This bug should need a fix from the development team. My suggestion would be to introduce a new event, OnCellChangesCancelled to be fired when the cell value is changed only to match with the old value, so that any subscribers may want to undo the changes applied in previously fired event OnCellValueChange.
Hi @Ravi PunjwaniThank you for your response.While waiting for the fix, is it possible to use JavaScript to override OnCellValueChange?
As I now finished a deep dive into the component's code, I feel a fair bit of customization will be required. Hence it won't be a simple javascript tweak to add a new event emitting from the web block. While others may have a different opinion about it, I would consider only to change if I won't break any existing code and would make sure the customized code goes in line with how the remaining code is written and maintained.
The customization will be required in Gridframework.js > class OnCellValueChange.
I suppose it would be the developer team who can integration this change better than others due to following their internal guidelines in making this work. If approved with this change, this may need propagating in other types of columns as well, I see you're using NumberColumn in this example. But this scenario exists in all editable columns types.