view definition 'parent'

This is the view definition of one2many field(account.voucher.line) under account voucher. You can use "parent" option to get the variables in parent object(here account.voucher). Here the use is to filter the account.voucher.line according to the partner selected on account.voucher.
You got error because you may try to use the parent option in the main view instead of one2many object's view under main model.

Hi mjabirk,

The code is below. Field move_line_id belongs to account_voucher_line.
===
<field name="line_cr_ids">
   <field name="move_line_id"
      context="{'journal_id':parent.journal_id, 'partner_id':parent.partner_id}"
      on_change="onchange_move_line_id(move_line_id)"
      domain="[('account_id.type','in',('receivable','payable')),
         ('reconcile_id','=', False),
         ('partner_id','=',parent.partner_id)]"
   />
  <field name='account_id' domain="[('company_id','=', parent.company_id)]"/> => here is my additional code
===

As you see, field account_id also belongs to account_voucher_line, but can't use 'parent'.

Thanks,

Hi mjabirk,

strange thing is that my code is understood when defining in account.voucher.receipt.form view but not understood in account.voucher.purchase.form view.

===
 <field name='account_id' domain="[('company_id','=', parent.company_id)]"/>
===

Do you have any suggestions?

Thanks,

After doing many tests, I found the reason. If using widget="selection", it will not support 'parent' option.

Hello,

Domain values that are written inside a view (or as a string value in the definition of a field) are meant to be evaluated at the client side. Therefore these may reference the fields values that are present in the form (but only those!), as well as the parent form if there is one. A domain in a view may look like [('partner_id', '=', parent.partner_id)], but it cannot following relationships that are known only on server-side, for example this will not work: [('address_id', '=', user_id.address_id)], because at the client-side 'user_id' is just an integer value, not a real relationship.
Note that in certain cases a domain will be specific in model as a Python list, which means that it should be evaluated server-side too (for example for some one2many fields)

Now there is a specific case for selection widget, because for a normal fields.selection, the available options are known in advance and directly provided by the server in the result of fields_view_get(). So when using a widget=selection for a many2one field, the server does a pre-computation of the possible values for the many2one, in order to provide that same list of options to the client.
So in that specific case, the server will evaluate the domain of the many2one on server-side, and this happens before the view is opened, so client-side field values or 'parent' values are not available.

This is currently the way it works, by design.

In the future we may provide a different mechanism to avoid this use of selection widgets for many2one fields, for example in v6.1 the new web client includes a new widget for many2one that can work using dynamic domains.