Contributors mailing list archives


Re: Operating in various companies simultaneously

LasLabs, Dave Lasley
- 13/06/2017 18:45:10
Regarding the property fields - take a look at our discussion in OCA/multi-company#39, where we attempted to work through some of these issues. I would love to see our multi company logic expanded- this is a serious pain point for me.

Take a look at our pass-through functionality in thebase_multi_company Abstract Model, which helps out with some of the independent logic on the models + provides a relational for company assignments that breach the standard security. I’ve been meaning to write up a ReadMe on this - it’s horribly documented right now.

— Dave Lasley

On Jun 13, 2017, at 9:38 AM, wrote:

Great initiative Jordi.

Note it might be hard to fix everything in modules. Ideally all these multi-company scenarios must be fixed in Odoo core because you also have crons running as admin which hits such bugs.

In my experience Odoo usually accepts patches for these issues. If not accepted in stable, propose them to Odoo master. 

You could keep an inventory of such PR's in an issue or wiki in OCA/multi-company..


On Tue, Jun 13, 2017 at 2:08 PM, Jordi Ballester Alomar <> wrote:
Dear OCA contributors,

We have started a project to implement in Odoo 10 the capability for users to be able operate on multiple companies simultaneously. 

As you all know, nowadays when a user has access to multiple companies she has to manually switch from one company to the other, to be able to operate on each. This is very frustrating for people that work on multiple companies at the same time.

Currently you can create a parent company if you want to have full visibility of the child companies, but users need to be warned not to operate on the parent companies, because they would be at risk of introducing lots of inconsistencies.

The project attempts to resolve two issues separately:

1. Existing bugs in Odoo. Attempts to fix the errors that you get in the processes if you operate in two companies simultaneously. For example, if you are creating an invoice associated to company B, the accounts available to the user should be from this same company. With this fixes a user should also be able to operate correctly Odoo, in the current swith-company approach. These bugfixes should ultimately land in Odoo core.

2. Maintain property fields from different companies simultaneously on a given model. For example, when you create a partner you want to assign the receivable and payable accounts to all companies for that partner.

Inline image 1

The project is under way at this moment, and proved the feasibility of the approach.

Currently we are hosting the code in the following repo:
The modules with prefix mcfix* handle the bufgixes
The modules with prefix multicompany* handle the simultaneous maintenance of property fields associated to a given model.

Next steps
1. Can we host the modules in
2. We need contributors to assist to review and complete the work. Identify new modules that need bugfixes, or require simultaneous property field management
3. We need agreement on the module naming conventions.

Jordi Ballester Alomar
CEO & Founder | Eficent

Post to: