As Olivier said, on picking, there is another ordering criteria that is important: preferred date, but I think there can be a compromise solution between both needs using specific ordering on some views. ¡Let's work on it for trunk!
About rich format sale orders (a better sale_layout module), is more than desirable, but I think it's another question out of this scope. Regards. 2013/9/24 Eric Caudal <eric.cau...@elico-corp.com> > +1 > > Eric Caudal*CEO* > --*Elico Corporation, Shanghai branchOpenERP Premium Certified Training > Partner * > Cell: + 86 186 2136 1670 > Office: + 86 21 6211 8017/27/37 > Skype: elico.corperic.caudal@elico-corp.comhttp://www.elico-corp.com > > [image: Elico Corp] > On 24/09/2013 19:26, ferdinand wrote: > > On 09/24/2013 01:09 PM, Olivier Dony wrote: > > On 09/24/2013 10:33 AM, Alexandre Fayolle wrote: > > * For invoices, the sequence field is there on the lines but not > editable, and only set by default from sale.orders AFAICT. > > > The preferred method to allow reordering lines is to simply add the > `sequence` field in the editable list view, using widget="handle", then not > to put it in the form view of the lines. > It seems to me this was added on both Supplier[1] and Customer[2] invoice > lines in 7.0, so no customization should be needed in this case. > > It would make sense to contribute the sequence fields to Pickings and > possibly POs in trunk (+sync code), as users expect this information to be > propagated during the whole ordering-invoicing-delivery flow. > By default I would not show the sequence and handle inside pickings > though, but only use it to order the stock moves. > However this conflicts with the current _order for moves, which is set to > 'date_expected desc, id' and is useful when moves are displayed outside of > their picking (quite common) - the sequence being relative to the > picking/context. Perhaps using > _order = 'date_expected desc, sequence, id' > would give an acceptable result in most cases? > > > IMO > > - sequence must be propagated from SO/PO - PICK - INV > - sequence is not enough as > > > Clients often request to structure offers, pickings, invoices > > 1. header 1 1000 > 1.2. pos1 600 > 1.3. pos 2 400 > > 2. header 2 300 > 2.1 pos 1 50 > 2.2 pos 2 250 > > total 1300 > > > > For v7 this stuff could live inside 2 trivial modules. > > Cheers, > > > [1] rev.9463 revid:m...@openerp.com-20130920095026-qv0o2ohcys8druf5 > [2] rev.9409 revid:m...@openerp.com-20130903125900-wl1r1etx9pyhe185 > > _______________________________________________ > 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 > > > > _______________________________________________ > 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 > >
<<elico_signature.jpg>>
_______________________________________________ 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
