On 14/02/13 21:16, Cédric Krier wrote:
On 14/02/13 21:10 +0100, Jordi Esteve wrote:
These criteria can be combined, for example to set an analytic
account for an specific partner and company.
I think this kind of module is very flexible and could be useful for
several people. It is worth to code it for Tryton.
As I already explain, such behavior doesn't add any information to the
system indeed it just duplicate it which is always bad.
So it does not solve the real issue which is? I don't know.
Sergi has explained it before: To propose automatically analytic
accounts in invoice lines, for example. Some companies fills
analytic accounts by user, by company, by partner, by product. For
the user is more comfortable and it prevents user errors.
Wrong design! Such information can be already found in the system, no
need otf analytic for that.
*Duplicate* information is always wrong.
Not always the information is duplicated. I said that it can *propose*
automatically analytic accounts in invoice lines, but then the user can
change the proposed analytic account with a different analytic account.
So the final analytic moves could be related to an user, a company, a
partner, a product, or not related to any of them.
--
Jordi Esteve
Consultor Zikzakmedia SL
[email protected]
Mòbil 679 170 693
Zikzakmedia SL
Dr. Fleming, 28, baixos
08720 Vilafranca del Penedès
Tel 93 890 2108
--
--
[email protected] mailing list
---
You received this message because you are subscribed to the Google Groups "tryton" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
