Comment 78 for bug 1160365

On 04/10/2013 02:49 PM, Guewen Baconnier @ Camptocamp wrote:
> 2. When you click on the *link* Claims because it uses a domain with a
> child_of. But what for the *one2many fields*, are you going to replace
> them all by a fields.function using a child_of instead of a = ?

Actually we plan to remove one2many fields from form views, it was a bad
usability approach. (we already have a branch that removed all remaining
in trunk) We removed a lot of them in v7 and replaced them by buttons in
the top right corner.

It's much better as it's faster, opens a new view in the breadcrum, with
a search and an easy (full screen) create/edit form view.

> Example: the one2many displaying the claims in the history tab of
> Camptocamp Group won't display the claims from other employees while the
> link will. If you need to create a link with a 'child_of' because you
> can't rely on the one2many fields, that's a pity.

We don't think "one2many inside forms" is the best way to go. But if you
absolutly want to do that, you will have to do a hack (that's part of
the cons when I say you have to balance pros and cons)

--
Fabien Pinckaers
CEO OpenERP
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com