I am creating a record using a button action that calls a create() method. But some computed fields are not being computed. I did some print statements in the compute function and they did not show in logs which means it is not being called. Is this normal behavior ?
신고된 질문입니다
4
답글
12769
화면
You need to add the dependent fields in @api.depends of the computed function so that it's called when the corresponding fields are modified on the create() function.
Also a dirty trick is to set store=False on your computed field which will ensure that the compute function is always called, at least on each record fetching.
this solution worked perfectly for me, @api.depends and store=False are both worked.
I see that compute works only for fields that is set on views(visible or not). Existing on view is the trigger compute function if not any @api.depends defined or store = False is set. I think this works like this because the value of computed field is needed to show to user. I realize that compute functions also works after create function works and record get it's ID unless computed field is called by another function before create function works. If you want to set value on create from code it is better to set default value with a lambda code.
Do you set the value of the dependent fields in your create()? If the dependent fields' values not set the computed function will not be triggered.
in reply to @Khalid Hazam , I already have @api.depends, the computed field is computed correctly when i create a record using the UI, the problem is when I call the create() from code
| 관련 게시물 | 답글 | 화면 | 활동 | |
|---|---|---|---|---|
|
4
3월 25
|
12215 | ||
|
1
2월 21
|
5146 | ||
|
4
10월 20
|
11664 | ||
|
1
6월 26
|
3020 | ||
|
1
4월 26
|
3491 |
compute fields wont be storing in the db, unless you haven't set store=True. Try opening corresponding view and see, whether the compute function is get called.
the field has store=True, and I am not creating the record from the view, i am creating it from python.
did you find the answer yet?