Skip to Content
This question has been flagged
many2oneon_changev7onchange
1 Respondre
5083 Vistes
Avatar
Moin

I have four many2one fields from which only one can be populated at a time so I set on_change events on each of them to clear other three fields if something is selected but there's a recursion problem; changing one field clears other fields which in turn clears the initial field.

How would one go about avoiding this?

Avatar
Descartar
Avatar
Moin
Autor Best Answer

After a lot of faffing about, solution turned out to be rather simple; all I had to do was to check whether the field is empty or not before executing the code body of on_change function, here's a little example:

def onchange_item1(self, cr, uid, id, item1_id=None, context=None):
    domain = {}
    value = {}

    if item1_id:
        #Clear all selections
        value = {'item2_id': False,}

    return {'domain': domain,
            'value': value}

def onchange_item2(self, cr, uid, id, item2_id=None, context=None):
    domain = {}
    value = {}

    if item2_id:
        #Clear all selections
        value = {'item1_id': False}

    return {'domain': domain,
            'value': value}
Avatar
Descartar
Related Posts Respostes Vistes Activitat
when i select the category in the sale list the regarding product must shown in the product id in the bill list by onchange
many2one onchange
Avatar
0
de des. 18
13
Access One2many field from onchange in v9
many2one one2many v7 onchange v9
Avatar
0
de jul. 16
3831
Onchange many2one partner_bank_id Solved
many2one onchange
Avatar
Avatar
1
de maig 16
4387
Preventing On change recursion
v7 onchange
Avatar
1
de març 15
5426
How does api.onchange works while create a record from trigger
on_change onchange compute
Avatar
Avatar
1
de maig 24
2565