>> - if a module already defined contact_id for another purpose, you have a
>> conflict
>>
> Well in the very rare cases (5 cases in the whole the official addons)
For the record, I was just checking this and there are none. I believe
the five occurrences of contact_id that you spotted are just variables
that are assigned a browse record and then used as follows:
>> - if a module already defined contact_id for another purpose, you have a
>> conflict
>>
> Well in the very rare cases (5 cases in the whole the official addons)
For the record, I was just checking this and there are none. I believe
the five occurrences of contact_id that you spotted are just variables
that are assigned a browse record and then used as follows:
event/ event.py: contact_id = addr_obj.browse(cr, uid, event.py: 'email' :contact_ id.email,
contact, context=context)
event/