<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> <a name="d-matrix-for-x2many-fields"></a> <h2>2D matrix for x2many fields</h2> <p>This module allows to show an x2many field with 3-tuples ($x_value, $y_value, $value) in a table</p> <div class="line-block"> <div class="line-block"> <div class="line">| $x_value1 | $x_value2 |</div> </div> <div class="line">:---: | :---: | :---: |</div> <div class="line">$y_value1 | $value(1/1) | $value(2/1) |</div> <div class="line">$y_value2 | $value(1/2) | $value(2/2) |</div> </div> <p>where <cite>value(n/n)</cite> is editable.</p> <p>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:</p> <img alt="Screenshot" src="/web_widget_x2many_2d_matrix/static/description/screenshot.png" /> <p>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. Note: The order of axis values depends on their order in the matrix you provide.</p> <a name="usage"></a> <h3>Usage</h3> <p>Use this widget by saying:</p> <pre> <code>&lt;field name=&quot;my_field&quot; widget=&quot;x2many_2d_matrix&quot; /&gt;</code> </pre> <p>This assumes that my_field refers to a model with the fields <cite>x</cite>, <cite>y</cite> and <cite>value</cite>. If your fields are named differently, pass the correct names as attributes:</p> <pre> <code>&lt;field name=&quot;my_field&quot; widget=&quot;x2many_2d_matrix&quot; field_x_axis=&quot;my_field1&quot; field_y_axis=&quot;my_field2&quot; field_value=&quot;my_field3&quot; /&gt;</code> </pre> <p>You can pass the following parameters:</p> <dl class="docutils"> <dt>field_x_axis</dt> <dd>The field that indicates the x value of a point</dd> <dt>field_y_axis</dt> <dd>The field that indicates the y value of a point</dd> <dt>x_axis_clickable</dt> <dd>It indicates if the X axis allows to be clicked for navigating to the field (if it's a many2one field). True by default</dd> <dt>y_axis_clickable</dt> <dd>It indicates if the Y axis allows to be clicked for navigating to the field (if it's a many2one field). True by default</dd> <dt>field_label_x_axis</dt> <dd>Use another field to display in the table header</dd> <dt>field_label_y_axis</dt> <dd>Use another field to display in the table header</dd> <dt>field_value</dt> <dd>Show this field as value</dd> <dt>show_row_totals</dt> <dd>If field_value is a numeric field, calculate row totals</dd> <dt>show_column_totals</dt> <dd>If field_value is a numeric field, calculate column totals</dd> <dt>field_att_&lt;name&gt;</dt> <dd>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 <cite>&lt;name&gt;</cite> passed in the option.</dd> </dl> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/162/8.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="example"></a> <h3>Example</h3> <p>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 <code>project.task</code> as our data model and point to it from our wizard. The crucial part is that we fill the field in the default function:</p> <pre> <code>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)</code> </pre> <p>Now in our wizard, we can use:</p> <pre> <code>&lt;field name=&quot;task_ids&quot; widget=&quot;x2many_2d_matrix&quot; field_x_axis=&quot;project_id&quot; field_y_axis=&quot;user_id&quot; field_value=&quot;planned_hours&quot; /&gt;</code> </pre> <p>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 through <cite>field_att_disabled</cite> option with a control field.</p> <a name="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <ul class="simple"> <li>it would be worth trying to instantiate the proper field widget and let it render the input</li> </ul> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/web/issues">GitHub Issues</a>. 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 welcomed feedback.</p> <a name="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Holger Brunn &lt;<a class="reference external" href="mailto:hbrunn&#64;therp.nl">hbrunn&#64;therp.nl</a>&gt;</li> <li>Pedro M. Baeza &lt;<a class="reference external" href="mailto:pedro.baeza&#64;tecnativa.com">pedro.baeza&#64;tecnativa.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>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.</p> <p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>