Behavior of button_change in One2Many tree

I have placed button_change in One2Many tree to do some calculation on the selected record. Once you click a button or make changes on any record, all buttons on all records become disabled. Is it possible to perform the calculation on multiple records before saving them?

By default buttons on One2Many are disable if the main record is unsaved.
Now I guess we could improve the behavior to disable only class button and not instance button.

That would be cool. Because you can change many records, but you can click a button on only one record before saving.

5 posts were split to a new topic: How to fill an issue as feature request