跳至內容
選單
此問題已被標幟
1 回覆
4770 瀏覽次數

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 self are obviously ignored.

Maybe it's more of a feature request?

頭像
捨棄
最佳答案

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

頭像
捨棄
相關帖文 回覆 瀏覽次數 活動
2
4月 25
2769
3
11月 24
17433
1
11月 22
2982
2
12月 19
8046
1
3月 19
3481