* Betr.: " Re: [tryton-dev] Converting 'move' from a Many2One to a One2One in account.invoice" (Mon, 5 Dec 2011 14:11:57 +0100):
> A Dilluns, 5 de desembre de 2011 10:46:58, Mathias Behrle va escriure:
> > > Well, there are two questions here: One is to make the relationship a
> > > One2One and the other one to add the field to account.move. For the
> > > former I think that it is better because that's simply the relationship
> > > that exists between Invoices and Moves. You cannot have an invoice with
> > > several moves nor a move with several invoices, so that makes sense to
> > > me.
> >
> > Not sure about that. Because right now we also have a 'link' from move
> > lines to invoices for Payment Lines. If you are consequent, you will also
> > want to browse from those (payment) moves to the invoice, i.e. you will
> > have to update that invoice field (or display it via function field or
> > whatever) on the move of the line. And from that on it is no more one2one.
> >
>
> It is still a One2One because the name of the relationship is different. One
> is the move of the invoice and the other one of the payment.
My point is: If you want to be able to browse from account moves to
their respective invoices, you will also want to do this from account moves
relating to payment lines. Finally you would want to know on any move, if the
current move is related in any way to an invoice and to which one. You would
have the original move of the invoice (payable/receivable) and the payment
move(s) pointing to one same invoice. Correct?
Making move - invoice a one2one would restrict you from being able to do the
above. You could only point from the payable/receivable move to the invoice.
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
