如何在创建函数中使用 odoo 的服务器端 onchange 方法？答案

【问题标题】：How can I use odoo's server side onchange method, inside a create function?如何在创建函数中使用 odoo 的服务器端 onchange 方法？
【发布时间】：2020-08-12 12:37:54
【问题描述】：

比如我要触发这个功能：

@api.onchange("fieldA")
def _onchange(self):
   for rec in self:
        random = rec.fieldB

onchange 函数的一般形式为：onchange(values, field_name, field_onchange)

子问题 1： 我要求 fieldB 已经可用。我是否将其传递给“值”参数？
子问题 2： 回答者能否提供一个合适的代码示例？

参考文献中给出的常见示例通常采用以下形式：

wizard = self.env['library.return.wizard']
values = {'borrower_id': self.env.user.partner_id.id}
specs = wizard._onchange_spec()
updates = wizard.onchange(values, ['borrower_id'], specs)
....
....
wiz = wizard.create(values)

但这在我的情况下不起作用..

感谢您的帮助！

【问题讨论】：

标签： odoo odoo-8

【解决方案1】：

终于明白了。有一些隐藏的陷阱：

self.onchange 实际上同时调用了@api.depends 和@api.onchange 修饰函数
values dict（self.onchange 的第一个参数）实际上有 2 种用途：请查看下面的代码
（观察）self.onchange 返回值字典，不包括未由通过 self.onchange 调用的函数修改的字段

您可以参考下面我的代码 cmets 了解更多详细信息。希望这对某人有所帮助。

 @api.model
    def create(self, vals):
        # SECTION: Trigger server-side onchange to initialize all child dependent values of qty_to_ship. More generally, to trigger all @api.onchange functions in this shipment.item model.
        
        stock_move = self.env['stock.move'].browse([vals['move_id']])
        # 'values' dict: (1) provide values of fields when used in calling onchange functions (2) indicate fields that we want a return value for after calling onchange
        # Note: some key-values are commented because related fields of move_id will be computed when we call self.onchange
        values = {
            # 'product_id': stock_move.product_id.id,
            # 'product_tmpl_id': stock_move.product_id.product_tmpl_id.id,
            'move_id': stock_move.id,
            'qty_to_ship': stock_move.product_uom_qty,
            'carton_qty': 0,
            'item_sub_total': 0,
        }
        specs = self._onchange_spec()
        # Note: self.onchange, triggers both @api.depends, @api.onchange decorated functions (this is not mentioned in any documentation)
        # Note: the order of the list (2nd arg) matters
        # move_id needed to: trigger def _assign_relational_fields
        # product_tmpl_id needed to: trigger def _compute_carton_single
        # qty_to_ship needed to: trigger other functions with @api.onchange('qty_to_ship') decorator
        updates = self.onchange(values, ['move_id', 'product_tmpl_id', 'qty_to_ship'], specs)
        value = updates.get('value', {}) 
        for name, val in value.items(): 
            if isinstance(val, tuple): 
                value[name] = val[0]
        vals.update(value)
        # insert qty_to_ship as it is not modified by any of the onchange functions triggered earlier. Hence it will not be attached to 'value' dict
        vals.update({'qty_to_ship': stock_move.product_uom_qty})

        # Continue with super create
        res = super(ACDShipmentItems, self).create(vals)

        return res

【讨论】：