This module allows to show an x2many field with 3-tuples (\$x_value, \$y_value, \$value) in a table
| | \$x_value1 | \$x_value2 | |------------|--------------|--------------| | \$y_value1 | \$value(1/1) | \$value(2/1) | | \$y_value2 | \$value(1/2) | \$value(2/2) |
where value(n/n) is editable.
An example use case would be: Select some projects and some employees so that a manager can easily fill in the planned_hours for one task per employee. The result could look like this:
The beauty of this is that you have an arbitrary amount of columns with this widget, trying to get this in standard x2many lists involves some quite ugly hacks.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds a new field widget that displays a list of related records as an editable 2D matrix, with one field on the horizontal axis, one on the vertical axis, and a value field in each cell.
This module provides a new field widget called x2many_2d_matrix that can be used on any x2many field (for example, a list of users on a group). Instead of showing the records as a normal list, it arranges them in a table: the values of one field become the columns, the values of another field become the rows, and a third field is shown and edited in each cell.
- The widget is configured in the view with three attributes:
field_x_axis,field_y_axis, andfield_value. The value field can be of type integer, float, monetary, char, boolean, selection, or many2one. - When the value field is numeric, the widget can show row totals, column totals, and a grand total. These totals are displayed by default but can be turned off with
show_row_totalsandshow_column_totals. - If the x or y axis field is a many2one, the axis labels can be made clickable to open the related record, using
x_axis_clickableandy_axis_clickable. - The widget respects the domain, required, and readonly settings defined on the fields inside the embedded list view. For example, a value field can be required only for certain rows or readonly for certain users.
- If there are no records, a message "Nothing to display." is shown.
The module only adds a frontend widget; it does not create new models or menus. It includes a demo view on the Groups form (res.groups) that shows several examples of the widget with different field types.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/web.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0Use this widget by saying:
This assumes that my_field refers to a model with the fields x, y and value. If your fields are named differently, pass the correct names as attributes:
<field name="my_field" widget="x2many_2d_matrix" field_x_axis="my_field1" field_y_axis="my_field2" field_value="my_field3">
<list>
<field name="my_field"/>
<field name="my_field1"/>
<field name="my_field2"/>
<field name="my_field3"/>
</list>
</field>You can pass the following parameters:
field_x_axis The field that indicates the x value of a point
field_y_axis The field that indicates the y value of a point
field_value Show this field as value
show_row_totals If field_value is a numeric field, it indicates if you want to calculate row totals. True by default
show_column_totals If field_value is a numeric field, it indicates if you want to calculate column totals. True by default
x_axis_clickable If the x axis field is a many2one field, render the values as links to the record in question
y_axis_clickable If the y axis field is a many2one field, render the values as links to the record in question
For the value field, you can set any attributes you'd set in a normal list view, ie if your value field is a many2one field and you want to disable creating records via this field, you'd write
<field name="my_field3" options="{'no_create': true}"/>or if you want to have a custom domain or context
<field name="my_field3" domain="[('some_field', '=', my_field1)]" context="{'default_some_field': my_field1}" />Note that to be able to refer to other fields than the ones used as coordinates or value, you have to add them inside the list node.
Example
You need a data structure already filled with values. Let's assume we want to use this widget in a wizard that lets the user fill in planned hours for one task per project per user. In this case, we can use project.task as our data model and point to it from our wizard. The crucial part is that we fill the field in the default function:
from odoo import fields, models
class MyWizard(models.TransientModel):
_name = 'my.wizard'
def _default_task_ids(self):
# your list of project should come from the context, some selection
# in a previous wizard or wherever else
projects = self.env['project.project'].browse([1, 2, 3])
# same with users
users = self.env['res.users'].browse([1, 2, 3])
return [
(0, 0, {
'name': 'Sample task name',
'project_id': p.id,
'user_id': u.id,
'planned_hours': 0,
'message_needaction': False,
'date_deadline': fields.Date.today(),
})
# if the project doesn't have a task for the user,
# create a new one
if not p.task_ids.filtered(lambda x: x.user_id == u) else
# otherwise, return the task
(4, p.task_ids.filtered(lambda x: x.user_id == u)[0].id)
for p in projects
for u in users
]
task_ids = fields.Many2many('project.task', default=_default_task_ids)Now in our wizard, we can use:
<field name="task_ids" widget="x2many_2d_matrix" field_x_axis="project_id" field_y_axis="user_id" field_value="planned_hours">
<list>
<field name="task_ids"/>
<field name="project_id"/>
<field name="user_id"/>
<field name="planned_hours"/>
</list>
</field>No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.