openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #09648
[Bug 969027] [NEW] Wish - it would be great to be able to change the content of a one2many list from an on_change event
Public bug reported:
This is not a bug but an enhancement/wish request.
It is possible to put an on_change attribute on a one2many field. The on_change handler is properly called.
However it is not possible to change freely the content of the one2many.
It is worth insisting on what I mean by 'freely'. You can send back an
array (e.g : [1,2,3] ) of ids but these must correspond to existing item
in the db.
Purpose. I stumbled on this trying to find a solution for the following
business case:
when a product is added to a sale order (new sale order line), related
products should be added to the sale order automatically (buty a pc, the
system adds a screen, a keyboard a mouse).
** Affects: openobject-server
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/969027
Title:
Wish - it would be great to be able to change the content of a
one2many list from an on_change event
Status in OpenERP Server:
New
Bug description:
This is not a bug but an enhancement/wish request.
It is possible to put an on_change attribute on a one2many field. The on_change handler is properly called.
However it is not possible to change freely the content of the one2many.
It is worth insisting on what I mean by 'freely'. You can send back an
array (e.g : [1,2,3] ) of ids but these must correspond to existing
item in the db.
Purpose. I stumbled on this trying to find a solution for the
following business case:
when a product is added to a sale order (new sale order line), related
products should be added to the sale order automatically (buty a pc,
the system adds a screen, a keyboard a mouse).
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/969027/+subscriptions
Follow ups
References