El 11/04/2014 0:25, "Cédric Krier" <[email protected]> va escriure: > > On 10 Apr 17:57, Iasmini - Gmail wrote: > > Em 10/04/2014 17:15, Cédric Krier escreveu: > > >On 10 Apr 16:11, Iasmini - Gmail wrote: > > >>What I want is: > > >>3 tables: financial_financial, financial_receivable and financial_payable > > >>3 classes: Financial, Receivable and Payable > > >>2 screens: Receivable and Payable with own fields and Financial > > >>fields on both. > > >> > > >>Is there a way to do this on Tryton? > > >No more. The feature was removed because it causes too much issues > > >regarding access rights, triggers and behavior. > > > > > >I think you should think about the database design. Why do you want 3 > > >tables? Why 2 tables are not enough? Or even just 1 table? > > >After that, you have to think about models, is the Financial has meaning > > >alone? etc. > > > > > Ok, I'll make one table, as was done in the product. > > But this way, there will be field in the financial table that makes > > sense only to receivable and vice versa. > > You can make them invisible in such case. > > > And if I were two tables, I would have to repeat the common fields at > > two each.
If a single register can't be payable and receivable at the same time, it doesn't matter. You won't have repeated data, only repeated structure. > But you can share the code between the two Models.
