odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[FIX] updates the graph view documentation 

It was wrong.
This commit is contained in:
Géry Debongnie 2014-10-31 09:43:56 +01:00
parent 95265e9ba6
commit 7ad4af89fe
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
addons/web_graph/doc/index.rst
View File

@ -103,7 +103,7 @@ The order is important: for example if two fields are grouped by row, then the f
Date/datetime
-------------
Dates and datetimes are always a little tricky. There is a special syntax for grouping them by intervals.
Dates and datetimes are always a little tricky. There is a special syntax for grouping them by intervals. Most of the time, the interval can be specified as a suffix:
* field_date:day,
* field_date:week,
@ -113,15 +113,20 @@ Dates and datetimes are always a little tricky. There is a special syntax for g
For example,
.. code-block:: xml
<filter string="Week" context="{'group_by':'date_followup:week'}" help="Week"/>
But to describe a graph view in xml, this would fail the xml validation ("date_followup:week" is not a valid field). In that case, the graph view can be described with an "interval" attribute. For example,
.. code-block:: xml
<graph string="Leads Analysis" type="pivot" stacked="True">
<field name="date_deadline:week" type="row"/>
<field name="date_deadline" interval="week" type="row"/>
<field name="stage_id" type="col"/>
<field name="planned_revenue" type="measure"/>
</graph>
Example:
--------
Here is an example of a graph view defined for the model *crm.lead.report*. It will open in pivot table mode. If it is switched to bar chart mode, the bars will be stacked. The data will be grouped according to the date_deadline field in rows, and the columns will be the various stages of an opportunity. Also, the *planned_revenue* field will be used as a measure.