I totally agree with Nicolas,
double read the party pattern http://www.tdan.com/view-articles/5014/
let's say now our party thing is the res.partner table/object.
It's not because companies, their contact and final customers now live in the same table that they should be always inter-changeable. They are not!!
Accouting, financial and fiscal data will be all wrong if you start invoicing contact Mr Foo.
Instead I suggest we put a domain on invoice partner_id field to forbid selecting a company contact. And as Nicolas suggest, we add a new contact_id field to carry the invoice contact.
Hello Frederic and Nicolas,
I totally agree with Nicolas, www.tdan. com/view- articles/ 5014/
double read the party pattern http://
let's say now our party thing is the res.partner table/object.
It's not because companies, their contact and final customers now live in the same table that they should be always inter-changeable. They are not!!
Accouting, financial and fiscal data will be all wrong if you start invoicing contact Mr Foo.
Instead I suggest we put a domain on invoice partner_id field to forbid selecting a company contact. And as Nicolas suggest, we add a new contact_id field to carry the invoice contact.
Regards.