Clicking a button in a form view brings one-to-many widgets back to the first record

Bug #1072784 reported by Numérigraphe
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo GTK Client (MOVED TO GITHUB)
Fix Committed
Undecided
OpenERP Publisher's Warranty Team

Bug Description

In v6.0 and v6.1 at least, when using a form view with a o2m widget, if you click a button, the o2m widget is reset to the first record.
This is particularly annoying when you have more than 10 records in the o2m list, and you want to click a button on each of them.

The attached screencast illustrates this. Please note that the problem also happens when you click a button on the "parent" form.

Lionel Sausin.

Tags: maintenance

Related branches

Revision history for this message
Numérigraphe (numerigraphe) wrote :
Changed in openobject-client:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
Revision history for this message
Ravi Gohil (OpenERP) (rgo-openerp) wrote :

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.

Changed in openobject-client:
status: New → Opinion
Revision history for this message
Numérigraphe (numerigraphe) wrote :

Dear Ravi Gohil,
Undoubtedly the data needs to be reloaded. But from a user's point of view, it is quite necessary that this does not send him "off the track" every time.
So the current "editing" state must be recorded, and restored when that form is reloaded.
Can it be done ?
Lionel.

Changed in openobject-client:
status: Opinion → In Progress
Revision history for this message
Numérigraphe (numerigraphe) wrote :

I'll add that the problem also happens when the o2m widget displayed as a list - please see the attached screencast.
Lionel.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

Progress is being made by the maintenance team. The current patch still falls short of solving the problem but it's encouraging.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

We sponsored the development of a fix (see branch attached). The branch can be merged into 6.0, 6.1 and the current trunk/future 7.0.
Lionel.

Changed in openobject-client:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.