.. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html :alt: License: AGPL-3 =========================== 2D matrix for x2many fields =========================== 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: .. image:: /web_widget_x2many_2d_matrix/static/description/screenshot.png :alt: Screenshot 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. Usage ===== Use 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: .. code-block:: xml 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_label_x_axis Use another field to display in the table header field_label_y_axis Use another field to display in the table header 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 .. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas :alt: Try me on Runbot :target: https://runbot.odoo-community.org/runbot/162/11.0 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: .. code-block:: python 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: .. code-block:: xml Known issues / Roadmap ====================== * Support extra attributes on each field cell via `field_extra_attrs` param. We could set a cell as not editable, required or readonly for instance. The `readonly` case will also give the ability to click on m2o to open related records. * Support limit total records in the matrix. Ref: https://github.com/OCA/web/issues/901 * Support cell traversal through keyboard arrows. * Entering the widget from behind by pressing ``Shift+TAB`` in your keyboard will enter into the 1st cell until https://github.com/odoo/odoo/pull/26490 is merged. * Support extra invisible fields inside each cell. Bug Tracker =========== Bugs are tracked on `GitHub Issues `_. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing a detailed and welcomed feedback. Credits ======= Contributors ------------ * Holger Brunn * Pedro M. Baeza * Artem Kostyuk * Simone Orsi * Timon Tschanz * Jairo Llopis * Dennis Sluijk Maintainer ---------- .. image:: https://odoo-community.org/logo.png :alt: Odoo Community Association :target: https://odoo-community.org This module is maintained by the OCA. OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use. To contribute to this module, please visit https://odoo-community.org.