On 2013-09-24 19:17,
antonio.seque...@multibase.pt wrote:
Yes, it looks like a very good solution (which has to implemented
/ extended for SO, PICK and INV)
the group record has obviously also to be linked to stock moves
and invoice lines to allow the same ordering and grouping in
pickings and invoices.
the subtotal for invoices (and pickings ?) must be an function
field to allow partial invoicing.
Hello,
We have developed the attached module to order Sales Order
lines, by creating a group of lines and give it a title and a
sequence inside the group - the name of the group is the
title.
The ordered lines are shown in the print form also
the group is created when entering the product. (order
line)
Comments are welcome.
Regards
António Sequeira
From:
"ferdinand" <off...@chricar.at>
To: openerp-community@lists.launchpad.net
Sent: Tuesday, 24 September, 2013 5:14:00 PM
Subject: Re: [Openerp-community] reorderable lines on
purchase.orders, account.invoice, stock.picking
On 09/24/2013 05:05 PM, Olivier Dony wrote:
> On 09/24/2013 01:38 PM, Alan Lord wrote:
>>
>>
https://lists.launchpad.net/openerp-community/msg01313.html
>>
>> (4th Oct 2012)...
>>
>> Interesting that Olivier said in his first reply to
this thread that "-
>> line ordering propagates throughout the workflow by
default"
>
> Yup, as mentioned, that was the plan. And it does
propagate from SO to
> Invoices, which is the part that was covered by the
> sale_layout/invoice_layout modules, IIRC.
>
> For trunk/v8 we're considering the options to support
titles, groups
> and subtotals in SOs/POs/Invoices, in a way that's
cleaner and more
> robust than the original *_layout hacks. But as Pedro
says, that's
> quite a different story!
> One option would be to add a generic "section" field on
all those
> lines objects. A section would represent a generic group
of lines,
> with a title and some extra flags (sequence number,
subtotal needed ,
> etc.). Then by implementing a true "group by" mechanism
within
> one2many lists we could offer a drag'n'drop support for
organizing the
> lists within sections, à la WYSIWYG.
>
>
>
> [1] That's harder than it seems - it requires client-side
> logic/grouping because some of the lines in a o2m may be
dirty or new,
> so the server would be unable to perform the sorting.
that's why the module one2many_sorted was created
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
--
 
web: http://www.multibase.pt
facebook:
https://www.facebook.com/multibase.portugal
linkedin: http://www.linkedin.com/company/multibase
twitter: @multibasept
Rua Bernardo Lima, Nº 47 - 6ºEsq -
1150-075 LISBOA
Tel:+351-217921420 -
Telemóvel:+351-969033267
A MULTIBASE é associada ESOP
(www.esop.pt) defendendo e promovendo ativamente os
conceitos de Software Aberto, Interoperabilidade, Normas
Abertas e Independência de Plataforma.
CONFIDENCIALIDADE /
RESPONSABILIDADE
Esta mensagem pode conter informação
confidencial e foi preparada para utilização exclusiva do(s)
destinatário(s) supra indicado(s). Informamos que as
mensagens enviadas por e-mail não se encontram
garantidamente isentas de erros, podendo ser intercetadas,
corrompidas, perdidas, ser parcial ou totalmente destruídas,
ou mesmo conter vírus. Assim, declinamos qualquer
responsabilidade por erros ou omissões no conteúdo das
mensagens transmitidas por esta via.
Antes de imprimir esta mensagem pense na
sua responsabilidade e compromisso com o MEIO AMBIENTE.
--
Ferdinand
|
