Hello. By design, the o2m (and the m2m) does not handle the required
flag. We do not consider that a 'required' x2m relationship would have
lot of sense.
** Changed in: openobject-client
Status: Confirmed => Invalid
** Changed in: openobject-client
Status: Invalid => Opinion
** Changed in: openerp-web
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of OpenERP
sa GTK client R&D, which is a bug assignee.
https://bugs.launchpad.net/bugs/1013636
Title:
[6.1, trunk] One2many widget does not honour being 'required'
Status in OpenERP Web:
Opinion
Status in OpenERP GTK Client:
Opinion
Bug description:
Hi,
both 6.1 and trunk do not signal correctly when a required one2many
field is being left empty.
An example from the base module is to go to Settings -> Technical ->
Database Structure -> Models. Create a new model, but do not enter any
fields. The model can be saved without an error message, even though
Fields is a required field on ir.model.
I would expect the client to raise an error 'The following fields are
invalid: Fields'
cheers,
Stefan.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openerp-web/+bug/1013636/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help : https://help.launchpad.net/ListHelp
