Hi, Following my attempt to improve the situation of multi-company [1], I faced so much problem that I only see to solution:
- a very complicate one where many things will become a list per
company. For example on product, the prices, the accounts etc.
This will make the code very complicate but also the user
interface.
- a very simple, drop company.
I start thinking that the last one is the right move even if it will
prevent none single company database to migrate.
What are the use case of multi-company?
- accounting consolidation
It is a reporting issue that should be fixed by BI
- sharing party
That's a good one if you forget that parties have many properties
directly linked to the company like the accounts, tax rules etc.
And I think this can be acheived by using a synchronisation of the
common data using for example the CardDAV or any other similar
protocol.
- sharing product
Quite similar to party expect that it has much more company related
properties.
So again it could be implemented using a synchronisation mechanism.
I know there are product description message in EDI, so it could be
a way.
I don't see any other cases.
So when I imagine the simplification of removing the company, I really
think it deserve the annoyance of breaking the migration.
And for such cases, a way to go could be to duplicate the DB and drop on
each the other the companies.
[1] https://bugs.tryton.org/issue4080
--
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
pgpFV5u2JVW6W.pgp
Description: PGP signature
