diff options
| author | Olivier Dony <odo@openerp.com> | 2013-08-21 13:58:22 +0200 |
|---|---|---|
| committer | Olivier Dony <odo@openerp.com> | 2013-08-21 13:58:22 +0200 |
| commit | c57b85ed535a33e4d3bb03c981ac9463d50714bc (patch) | |
| tree | 701eeafa324549edce7aee05ccaad59893d4560e /doc | |
| parent | 7ce2c64eb4c67aef876427a1159f80e83d28e998 (diff) | |
[DOC] minor wording/formatting/nitpicking on top of previous patch
bzr revid: odo@openerp.com-20130821115822-kd9d8m1upvo5wiux
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/03_module_dev_03.rst | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/03_module_dev_03.rst b/doc/03_module_dev_03.rst index b7a23b81385..fd82f36bff1 100644 --- a/doc/03_module_dev_03.rst +++ b/doc/03_module_dev_03.rst @@ -1351,21 +1351,22 @@ When you add a one2many field in a form view, you do something like this : If you want to specify the views to use, you can add a *context* attribute, and specify a view id for each type of view supported, exactly like the action's -*view_id* attribute: +*view_id* attribute, except that the provided view id must always be +fully-qualified with the module name, even if it belongs to the same module: .. code-block:: xml <field name="order_line" colspan="4" nolabel="1" - context="{'form_view_ref' : 'module.view_id', - 'tree_view_ref' : 'module.view_id'}"/> + context="{'form_view_ref': 'module.view_id', + 'tree_view_ref': 'module.view_id'}"/> .. note:: - You have to put the module name in xml id of the view, because this + You *have to* put the module name in the view_id, because this is evaluated when the view is displayed, and not when the XML file is parsed, so the module name information is not available. Failing to do so will result in the default view being selected (see - below). + below). If you don't specify the views, OpenERP will choose one in this order : |