summaryrefslogtreecommitdiff
path: root/doc/reference
diff options
context:
space:
mode:
authorChristophe Simonis <chs@odoo.com>2018-09-14 16:00:17 +0200
committerChristophe Simonis <chs@odoo.com>2018-09-14 16:00:17 +0200
commit9c77066f345360429a0920ca4d17af1f84a7ebea (patch)
tree469494018b2da134a8ddb5f51930566c1d39bf8e /doc/reference
parent5c11e0d6f9dcc2161735ce3fb93430b767d54cf9 (diff)
parent6c103589c15dcf97603f3e2909871cb1fefd6484 (diff)
[MERGE] forward port branch saas-11.4 up to 6c103589c15
Diffstat (limited to 'doc/reference')
-rw-r--r--doc/reference/views.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/reference/views.rst b/doc/reference/views.rst
index 5dcac794ec2..052c63a97f5 100644
--- a/doc/reference/views.rst
+++ b/doc/reference/views.rst
@@ -957,6 +957,18 @@ sorted on the string of the field.
which means that non-stored function fields can not be used in pivot views
+In Pivot view a ``field`` can have a ``widget`` attribute to dictate its format.
+The widget should be a field formatter, of which the most interesting are
+``date``, ``datetime``, ``float_time``, and ``monetary``.
+
+For instance a timesheet pivot view could be defined as::
+
+ <pivot string="Timesheet">
+ <field name="employee_id" type="row"/>
+ <field name="date" interval="month" type="col"/>
+ <field name="unit_amount" type="measure" widget="float_time"/>
+ </pivot>
+
.. _reference/views/kanban:
Kanban