On 07/21/2012 01:53 PM, Antony Lesuisse (OpenERP) wrote:
> This is a feature request according to our policy. And yet, not a very
> useful one, as in most case, you want users to be able to save draft
> versions of a document without lines. If you really need this behaviour
> you may override write().

Hello Antony,
particular behaviors can be certainly handled by write method. These 
will be implementation choices.
But if developer sets the field to be *required=True* (as per Stefan's 
example of *ir.model* model: *'field_id': 
fields.one2many('ir.model.fields', 'model_id', 'Fields', required=True)* 
), why should the user be able to create a model without fields?


-- 
Lorenzo Battistini

-- 
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:
  Confirmed
Status in OpenERP GTK Client:
  Confirmed

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

Reply via email to