Contributors mailing list archives
Re: Operating in various companies simultaneouslyby
Tecnativa. S. L., Pedro M. Baeza
I see these modules very dangerous and error-prone, as any module that adds new fields with multi-company purposes that are not covered by these multi-company tricks will fail, needing a lot of glue modules or patching the module itself. Example: https://github.com/OCA/sale-workflow/tree/8.0/sale_order_type. This module may select an incorrect sale order type depending on the current company and the company you want to create the sales order for.
I'm not sure if handling the issues generated by this on OCA should be a lot of overhead.
2017-06-13 17:23 GMT+02:00 Joël Grand-Guillaume <firstname.lastname@example.org>:
+1 to host under oca umbrellaLe 13 juin 2017 15:08, "Oleg Kuryan" <email@example.com> a écrit :Jordi, great initiative! It is 100% should be under OCA (if not even default Odoo as it is pretty irritates customers because not working properly).On Tue, Jun 13, 2017 at 3:38 PM Torvald Baade Bringsvor <firstname.lastname@example.org> wrote:Great news Jordi. I'm having all kinds of issues on this these days since all my customers seem to be multi company. Count me in.-Torvald2017-06-13 14:08 GMT+02:00 Jordi Ballester Alomar <email@example.com>: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.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 bufgixesThe modules with prefix multicompany* handle the simultaneous maintenance of property fields associated to a given model.Next steps1. Can we host the modules in https://github.com/OCA/multi-c
ompany?2. We need contributors to assist to review and complete the work. Identify new modules that need bugfixes, or require simultaneous property field management3. We need agreement on the module naming conventions.--///
Technical Director, XPANSA Group | ERP, BI, E-commerce, Data Mining and DMS consulting