From 7ad4af89fec7e63191ef89027530f0881150c0f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=A9ry=20Debongnie?= Date: Fri, 31 Oct 2014 09:43:56 +0100 Subject: [PATCH] [FIX] updates the graph view documentation It was wrong. --- addons/web_graph/doc/index.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/addons/web_graph/doc/index.rst b/addons/web_graph/doc/index.rst index be5c0a9f88c..8305dddfc44 100644 --- a/addons/web_graph/doc/index.rst +++ b/addons/web_graph/doc/index.rst @@ -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 + + + +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 - + - 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.