We discovered a very serious bug in the SetRow() functionality.
Click on a computed field in another row than current (in the Clicked event there is a SetRow(row) ) - move the mouse away of the field( computed you just clicked on) - and the value of the previous row is shown in the current rows "input field"
Seems you can bypass it with a Post SetRow() - but whar will this break - and how many places do you have to do this (if possible)
We are making a bug example to post to support - but the are having Chinese Holiday and will first be back later this month. (Hope the development team will be working :) )
Bug report #768 (edited)
Seems we have to revert to 2017 - leaving all the GIT fun behind - :( :( :(