Package: odoo9-addon-web-widget-x2many-2d-matrix
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)wherevalue(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.Table of contentsUsageExampleKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersUsageUse this widget by saying:<field name="my_field" widget="x2many_2d_matrix" />This assumes that my_field refers to a model with the fieldsx,yandvalue. 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" />You can pass the following parameters:field_x_axisThe field that indicates the x value of a pointfield_y_axisThe field that indicates the y value of a pointfield_label_x_axisUse another field to display in the table headerfield_label_y_axisUse another field to display in the table headerx_axis_clickableIt indicates if the X axis allows to be clicked for navigating to the field
(if it’s a many2one field). True by defaulty_axis_clickableIt indicates if the Y axis allows to be clicked for navigating to the field
(if it’s a many2one field). True by defaultfield_valueShow this field as valueshow_row_totalsIf field_value is a numeric field, it indicates if you want to calculate
row totals. True by defaultshow_column_totalsIf field_value is a numeric field, it indicates if you want to calculate
column totals. True by defaultfield_att_<name>Declare as many options prefixed with this string as you need for binding
a field value with an HTML node attribute (disabled, class, style…)
called as the<name>passed in the option.ExampleYou 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 useproject.taskas our
data model and point to it from our wizard. The crucial part is that we fill
the field in the default function: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, {'project_id': p.id, 'user_id': u.id, 'planned_hours': 0})
           # 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" />Note that all values in the matrix must exist, so you need to create them
previously if not present, but you can control visually the editability of
the fields in the matrix throughfield_att_disabledoption with a control
field.Known issues / RoadmapIt would be worth trying to instantiate the proper field widget and let it render the inputLet the widget deal with the missing values of the full Cartesian product,
instead of being forced to pre-fill all the possible values.If you pass values with an onchange, you need to overwrite the model’s methodonchangefor making the widget work:@api.multidefonchange(self,values,field_name,field_onchange):if"one2many_field"infield_onchange:forsubin[<field_list>]:field_onchange.setdefault("one2many_field."+sub,u"")returnsuper(model,self).onchange(values,field_name,field_onchange)Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us smashing it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTherp BVTecnativaContributorsHolger Brunn <hbrunn@therp.nl>Pedro M. Baeza <pedro.baeza@tecnativa.com>MaintainersThis 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.This module is part of theOCA/webproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.