1. Mailing Lists
  2. Contributors
  3. Re: Operating in various companies simultaneously

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Operating in various companies simultaneously

Re: Operating in various companies simultaneously

Avatar

Re: Operating in various companies simultaneously

by
Bringsvor Consulting AS, Torvald Bringsvor
- 15/06/2017 00:22:15
Good evening all.

Just discovered another issue that needs adressing I think.

Look at https://github.com/odoo/odoo/issues/11973

I don't understand Fabien's response here, it should be possible to have a product shared between companies and therefore it should be possible to have taxes dependant upon company like expense and income accounts are IMHO.

Workaround for now would be to define taxes for both company A and B on the product, since Odoo filters them anyway, but it seems cumbersome.

-Torvald


2017-06-14 16:37 GMT+02:00 Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>:
Hi there,


I share Jordi's vision here I must say. We need to move ahead on this topic to reach bigger company and sharing effort within the OCA make a lot of sense. 

That being said, the point that Pedro raise need to be address. I like the idea of having a PR among Odoo for each case.

Regards,

Joël

 

On Wed, Jun 14, 2017 at 7:53 AM, Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:
Dave, Pedro.

I velieve that that base_multi_company attempts to resolve a different problem. The availability of certain models to various companies simultaneously.

But what our proposal intends to solve is for a user to be able to carry out operations (e.g. Sales, pickings, invoices) regardless of what company they fall in.

What must be ensured is a consistent flow. E.g. You cannot create a sales order for company A that refers tp a warehouse from company B. Basic, fundamental consistence of the processes.

I agree with Pedro that the modules that provide bugfixes would call for many potential glue modules to other OCA modules. But remember that the final intention is for these bugfix modules to disappear once they are merged in Odoo code upstream.

We could build a policy overnance rule for the project that requires that any bugfix module requires a corresponding PR for the bugfix it provides to Odoo core, so that there will be a clear roadmap.


When the bugfixes have been attended by Odoo, S.A in core, there will not be a problem anymore with OCA modules.


While this does not occur, integrators shoyld be warned of the potential implications of using the modules. 

And I am sure that many will weight the options and choose to build  few extra glue modules, towards achieving the greater benefits of a truly sinultaneous multicompany operation.


As for the bugfixes, they are very small, compared to the potential benefits they provide, so it is in the best interest of Odoo, S.A to consider them.

IMHMO the current multi-company approach may be good for dad and pop shops, but is a barrier entry to larger Odoo implementations.

On Jun 13, 2017 7:08 PM, "David Lasley" <dave@dlasley.net> wrote:
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, Bidoul@pad.odoo-community.org 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..

-sbi

On Tue, Jun 13, 2017 at 2:08 PM, Jordi Ballester Alomar <jordi.ballester@eficent.com> 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 https://github.com/OCA/multi-company?
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.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager


_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe


Reference