From d2449dbdd09154ca0c8b3e3427b6dff5683b7343 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20BEAU?= Date: Tue, 12 Jun 2018 11:53:31 +0200 Subject: [PATCH] [IMP] update readme --- onchange_helper/README.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/onchange_helper/README.rst b/onchange_helper/README.rst index f7753dcf3..c30d33249 100644 --- a/onchange_helper/README.rst +++ b/onchange_helper/README.rst @@ -30,9 +30,11 @@ You can also use it on existing record for example: `vals = sale.play_onchanges(vals, ['partner_shipping_id'])` -Then the onchange will be played with the vals passed and the existing vals of the sale. `vals` will be updated with partner_invoice_id, pricelist_id, etc... +Then the onchange will be played with the vals passed and the existing vals of the sale. `vals` will be updated with partner_invoice_id, pricelist_id, etc.. +Behind the scene, `play_onchanges` will execute **all the methods** registered for the list of changed fields, so you do not have to call manually each onchange. To avoid performance issue when the method is called on a record, the record will be transformed into a memory record before calling the registered methods to avoid to trigger SQL updates command when values are assigned to the record by the onchange + Bug Tracker ===========