I get your point - so basically you propose a three layer model, where the current Party stands for Contacts, addresses are just, well, addresses (physical, invoice, postal, whatever), and there is a meta- level to aggregate Parties, as required. This does make sense and offers the highest degree of flexibility, the only issue being that the meta-level is not quite there yet. The "crutch" of using the trytond-party_communication module works for most situations, but is admittedly, in the above sense, not scalable. Is there any work on the meta-level in the make? Thanks a lot everybody! Chris
- Re: [tryton] Contact Mechanisms - per Par... Cédric Krier
- Re: [tryton] Contact Mechanisms - per... Raimon Esteve
- Re: [tryton] Contact Mechanisms - per Party versus... Jesús Martín Jiménez
- Re: [tryton] Contact Mechanisms - per Party versus... Raimon Esteve
- [tryton] Re: Contact Mechanisms - per Party versus... Chris Larsen
- Re: [tryton] Re: Contact Mechanisms - per Par... Axel Braun
- Re: [tryton] Re: Contact Mechanisms - per... Cédric Krier
- Re: [tryton] Re: Contact Mechanisms -... Guillem Barba Domingo
- Re: [tryton] Re: Contact Mechanisms - per... Raimon Esteve
- Re: [tryton] Re: Contact Mechanisms - per Par... Cédric Krier
- [tryton] Re: Contact Mechanisms - per Par... Chris Larsen
