El 20/12/13 12:29, Mathias Behrle ha escrit:
This could be a solution, but in the discussion until now there is one
show-stopper for me. You write:
> >>>>> > >>>account_es have accounts (A, A1, A2, B, B1, B2)
> >>>>> > >>>account_es_pyme have accounts (A, A1,A2, C, C1)
> >>>>> > >>>
> >>>>> > >>>On both cases numbered accounts are child of their letters
> >>>>> > >>>accounts. Also the name of the account A2 is different on both
> >>>>> > >>>charts, so they have the same code, but can be considered as
> >>>>> > >>>different accounts.
AFAIS the accounts are not really common, if they have different names.
And also wrote that this was some example, in the real chart of accounts
there is more than 1000 accounts in common.
>Will this module fit in tryton core modules? If so, i will try to work
>on in in the following days.
You would at least have to take care, that the selection process and overidden
create doesn't have an effect on the other charts.
That's the objective.
Finally I don't know, if the deduplication of data is really worth the effort
in those cases. In my view I would also stick to different modules as ced
proposed, evtl. depending on a common (taxes etc.) module, if they contain the
same records.
As exposed previously, it's difficult to mantain dependencies with two
modules.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
