On May 21, 4:02 pm, Cédric Krier <[email protected]> wrote:
> > Instead Eval should evaluate one2many like many2many with a list of ids. > I agree, because it was our first idea. But it implies to change how the client manage one2many fields. Now one2many fields are seen as a list of dictionaries, which is perfect for on_change methods because we can evaluate fields data even if not yet saved. If we change that to a list of ids, what would be sent as values in on_change methods (like on_change_lines on purchases or sales) ? B. -- [email protected] mailing list
