[FIX] crm,doc: remove whitespace in view_mode
Fixes 4 actions where a whitespace was inserted in the view_mode, resulting in
an unknown view_mode (' graph') in the view_switcher.
Also updates the doc to prevent people to think they can insert whitespaces in
the view_mode definition.
This commit is contained in:
@@ -150,7 +150,7 @@
|
||||
<field name="name">Pipeline Analysis</field>
|
||||
<field name="res_model">crm.opportunity.report</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">pivot, graph</field>
|
||||
<field name="view_mode">pivot,graph</field>
|
||||
<field name="context">{'search_default_opportunity': True, 'search_default_current': True, 'active_test': True}</field>
|
||||
<field name="view_ids"
|
||||
eval="[(5, 0, 0),
|
||||
@@ -169,7 +169,7 @@ teams of the sales pipeline.</field>
|
||||
<field name="name">Leads Analysis</field>
|
||||
<field name="res_model">crm.opportunity.report</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">pivot, graph</field>
|
||||
<field name="view_mode">pivot,graph</field>
|
||||
<field name="context">{'search_default_current': True, 'active_test': True}</field>
|
||||
<field name="view_ids"
|
||||
eval="[(5, 0, 0),
|
||||
|
||||
@@ -64,7 +64,7 @@
|
||||
<field name="name">Leads Analysis</field>
|
||||
<field name="res_model">crm.opportunity.report</field>
|
||||
<field name="context">{"search_default_month":1}</field>
|
||||
<field name="view_mode">pivot, graph</field>
|
||||
<field name="view_mode">pivot,graph</field>
|
||||
<field name="view_id" ref="crm.crm_opportunity_report_view_pivot_lead"/>
|
||||
<field name="domain">[('type', '=', 'lead'),('team_id', '=', active_id)]</field>
|
||||
<field name="context">{'active_test': True}</field>
|
||||
@@ -74,7 +74,7 @@
|
||||
<record id="action_report_crm_opportunity_salesteam" model="ir.actions.act_window">
|
||||
<field name="name">Pipeline Analysis</field>
|
||||
<field name="res_model">crm.opportunity.report</field>
|
||||
<field name="view_mode">pivot, graph</field>
|
||||
<field name="view_mode">pivot,graph</field>
|
||||
<field name="view_id" ref="crm.crm_opportunity_report_view_pivot"/>
|
||||
<field name="domain">[('type', '=', 'opportunity'), ('team_id', '=', active_id)]</field>
|
||||
<field name="context">{'active_test': True}</field>
|
||||
|
||||
@@ -101,9 +101,8 @@ In-database window actions have a few different fields which should be ignored
|
||||
by clients, mostly to use in composing the ``views`` list:
|
||||
|
||||
``view_mode``
|
||||
comma-separated list of view types (tree, form, ...) as a string. All of
|
||||
these types will be present in the generated ``views`` list (with at least
|
||||
a ``False`` view_id)
|
||||
comma-separated list of view types as a string. All of these types will be
|
||||
present in the generated ``views`` list (with at least a ``False`` view_id)
|
||||
``view_ids``
|
||||
M2M\ [#notquitem2m]_ to view objects, defines the initial content of
|
||||
``views``
|
||||
|
||||
Reference in New Issue
Block a user