Skip ke Konten
Menu
Pertanyaan ini telah diberikan tanda
3 Replies
6468 Tampilan

Hi everyone, another question. I am trying to setup a compute field that depends on the first_name attribute of my Person model, and has the value "Hi, ". I was able to achieve it in the following way, by looping through the "self" recordset:

```

hello_msg = fields.Char(string="hello", compute='_test_hello')

@api.depends("first_name")

def _test_hello(self):   

    for rec in self:      

        rec.hello_msg= 'Hi, ' + rec.name

``` 

However, it seems like any time I enter my list view, this field is recomputed for ALL my records, not just the one that I changed in the form view. This is just a toy problem, but for my actual use cases, this will cause a significant computational overhead. I wanted to trigger this function ONLY when a record changes, and only for that record.

Is there a way to achieve this?

Thanks


Avatar
Buang
Jawaban Terbai

Hi Fred,

hello_msg = fields.Char(string="hello", compute='_test_hello', store=True)

update hello_msg field as storable, then compute function triggers only when the dependent field changes.

Regards

Avatar
Buang
Penulis Jawaban Terbai

@Rinkal thanks for your reply. However, I've tried doing it and it still triggered every time I entered the list view.

A couple more questions:

* doesn't your example iterate through all records anyway? Is there a way to target the single record that changes, instead of iterating through the self recordset?

* what is the point of  compute='_test_hello' on my original example? If we are manually assigning the a value to rec.hello_msg inside the function, we could very well assign values to other attributes, which makes me think that the compute field is useless? 

Avatar
Buang
Jawaban Terbai

Hello,

You can use onchange() method instead of the compute method.

@api.onchange("first_name")
def _test_hello_based_on_change(self):
    for rec in self:
        rec.hello_msg= ''
        rec.hello_msg= 'Hi, ' + rec.name

Avatar
Buang
Post Terkait Replies Tampilan Aktivitas
1
Jun 25
15488
3
Apr 25
5696
Compute Fields Diselesaikan
2
Jul 24
3371
1
Jan 24
1864
1
Jul 22
2292