Comment 77 for bug 1073087

Oops, I apologise for my previous post (now hidden), obviously it was
only for a colleague who is also struggling with this multi-company issue.

I'm sorry for using the words that I used, I did not meant them to be as
insulting as they would have come across.

What I was trying to get across was that it seems redundant to have two
fields if they are required to have the same value to avoid errors.
That if we keep them as meaning 'works for' and 'working on' then we can
have a more versatile solution. The last bugfix submitted here appears
to be working for us in that regard so far.

Apologies again,

On 11/05/13 10:08, Ian Beardslee wrote:
> Ouch, if I understand Olivier in #73 correctly, that makes OpenERP well
> and truly broken for use in a Multi-company environment .. it actually
> just creates a database that can hold a number of companies.
> Our example of how it needs to work ..
> CompanyA (biggest company of a group, a lot of the additional support comes from here accounts payroll)
> CompanyB (smaller company hat replies on CompanyA for some business support)
> UserA (accounts person employed/paid by CompanyA, but also processes
> invoices for CompanyB)
> Our take on this is that UserA is employed by CompanyA (and works FOR
> them, paid by them) but also does work ON CompanyB's invoices. They use
> the preferences to change what company they will be working on at the
> time (so they only see that companies clients, invoicing etc) .
> If I understand it correctly, what Olivier is suggesting is that when
> changing the preferences that UserA wouldnow essentially be seen that
> they are now working for CompanyB while the are processing their
> accounts.
> That is going to cause a mess if while they are doing that someone needs
> to create a report about employees in CompanyA .. leave owed, across the
> board payrise. UserA will be excluded from all that. Or imagine if
> while UserA is 'working' for CompanyB, someone deducts the 3 days leave
> from everyone that CompanyB had closed during Xmas/NewYear.
> Going through the list of people and manually is NOT a feature of an ERP
> system.
> Unless there is some other way to differentiate how UserA is employed by
> CompanyA, but at that point in time is doing some process for CompanyB.