Comment 60 for bug 1160365

Hi Fabien

>So, if you want to define hierarchies of companies:
>
> - Camptocamp Group [is company]
> - Camptocamp Switzerland [is company]
> - Joël
> - Camptocamp France [is company]
> - Marc
> - Cécile, Accounting Department

So finaly all of this change for simply invoicing a "special" partner with your solution?
Keeping the solution with 2 fields I think wil be simplier and easier for user

Indeed in the partner_id will be able to put "Camptocamp Group", "Camptocamp France", "Camptocamp Switzerland"
and in the contact_id we will be able to put "Joel", "Marc", "Cécile".
If you only want to allow the user to set "Cécile" than we can simply add a type for the contact of a company (sale department, accounting departement....) and add a filter on the contact_id of an invoice.

With this solution you will avoid to change a lot of code and to have a datamodel more complicated.
Also you will not break the "group_by" because the user will randowly invoice "Camptocamp France" or "Cécile, Accounting Département"

For simple case you can only keep one field and you have the same behaviour without changing all of the code logic

Please never forgert "KISS" "Keep It Simple and Stupid"

>No: This reminds me the GTK discussions; everyone wanted to maintain
>GTK, fork, stay on v6.1, ... At the end, focusing on one clean web
>client was one of the most important move OpenERP did in the pasts months.

This is really different with the GTK discution, because in this case the majority of partner was agree with dropping the GTK client, and some partner was asking for maintaining it. But this time I don't see any OpenERP agree with you, and this is REALLY DIFFERENT.

Please take your time before merging a solution. We are in the same boat

Thanks you