Greetings,

We found that if you use a min value in a editable number column inside a datagrid and you change the value that the min value is beeing forced as a max value during runtime.

See for instance the attached OML. In Runtime: change the number in the Stock column. As you navigate out of the column the value of the changed column jumps to the min value (in this case).

We found out that this only occurs if you do not fill a Max value. perhaps the grid checks if the inserted value is between 1 and 0? We fixed this issue for now by updating the max value, but do not believe this is the expected behavior when only defining a min value

Cheers,

Jørgen