Comment 2 for bug 1072784

Hello Lionel,

Thanks for sharing the video with us.

The reason why this happens is, when you perform any action on o2m widget, the parent record is reloaded and in turn the child is reloaded too, that is why the o2m is reset to the first record.

Parent needs to be refreshed in case when the result of any action is to be reflected in the parent record itself.

Considering the case of `Manufacturing Orders`, there are two o2m, `Stock Moves` and `Consumed Products`. When you process the stock moves, they are moved to `Consumed Products`. Here, to move the component on the fly to consumed products, parent record needs to be reloaded.

This bug needs discussion from the experts, so I request the experts to share their opinion on this topic, meanwhile, I am changing the bug status to `Opinion`.

@experts: would you please share your views on this.

Thanks.