API 8.0 onchange() and depends() decorators only work for UI changes and 1 record only?

Question

Instead of calling *update_some_regular_fields()* method at the end of overwritten *create()* and* write()* methods, why can't I just decorate *update_some_regular_fields()* method with @*api.onchange()* or *@api.**depends()*? This would shorten the code considerably and make it readable, but the decorators seem to only react on changes from UI and ignore all other programmatic changes to DB records.

Also, with *self* being a virtual record in the onchange method, changes to records other than

Mind And Go · Answer

Hy,

For the onchange, it's legitim to consider that only one 1 record must be concerned because it's about client behaviour.
For the depends, I think it shoudl be compute one by one but could be done on multiple records. (eg via mass editing)
regards

Powiązane posty	Odpowiedzi	Widoki
Return multiple domain modification from one onchange() api onchange domains	2 kwi 25	3034
when i use @api.model? Rozwiązane api onchange model	3 lis 24	18219
Execute @api.onchange only once? api onchange odoo	1 lis 22	3250
Display many2many Field data into one2many field api onchange odoo12	2 gru 19	8269
How to create in v10 an invoice line from code with only [product_id, invoice_id, quantity and price_unit] Rozwiązane api onchange v10	1 mar 19	3649

To pytanie dostało ostrzeżenie

Podoba Ci się ta dyskusja? Dołącz do niej!