Comment 13 for bug 1155679

Hello,

well in my first comment I proposed 1) and 2) but nobody from OpenERP SA answered so I implemented 2) after advice from community.

That's true, the journal entries were taken correctly even if the quote and invoice were linked to the Joe contact.

Now, us and several people still find it very cumbersome to manage your opportunities, orders and invoices BY COMPANY if they point to some company contacts instead.
Say you take a list of opportunities|orders|invoices in OpenERP list view and do some group by partner, it won't aggregate things by companies. It makes all reporting a lot more cumbersome as you should look for some potential parent company.

As Ana and me suggested, we would have preferred to have the opportunity related to the company, still also mentioning the contact.
Without guidance from OpenERP SA, my change tried to stay minimalist and avoided touching the schema, say to have more chances to get into the stable branch.
That's why I didn't add a contact_id field to the opportunity entity (you still have the contact details in the 'prospect' tab anyway). But for me the best solution (may be not compatible with inclusion into stable then) would have been to add such contact_id field and propagate it to the created quote as the quote contact where the invoice is mailed also.

So in a word, yes, unlike what I said journal entries aren't screwed, but still we think putting the company as the partner_id at least for the quote and invoice would easy the management by companies later. So a solution could also be to extend my solution to also propagate the contact to the quote in order to avoid losing it, but still assigning the partner_id to the company. What do you think?