IRC logs of #tryton for Monday, 2016-01-04 #tryton log beginning Mon Jan 4 00:00:01 CET 2016
2016-01-04 00:13 -!- circ-user-A1ygf(~circuser-@ has joined #tryton
2016-01-04 02:00 -!- bechamel( has joined #tryton
2016-01-04 02:10 -!- bechamel1( has joined #tryton
2016-01-04 02:14 -!- bechamel( has joined #tryton
2016-01-04 03:30 -!- apostatize(~visavis@unaffiliated/apostatize) has joined #tryton
2016-01-04 03:57 -!- circ-user-A1ygf(~circuser-@ has joined #tryton
2016-01-04 06:02 -!- yangoon1( has joined #tryton
2016-01-04 07:40 -!- Telesight( has joined #tryton
2016-01-04 07:40 -!- frispete( has joined #tryton
2016-01-04 07:59 -!- dj_xatra(~dj_xatra@ has joined #tryton
2016-01-04 08:23 -!- tbruyere( has joined #tryton
2016-01-04 08:23 -!- Timitos( has joined #tryton
2016-01-04 09:01 -!- mrichez( has joined #tryton
2016-01-04 09:14 -!- udono( has joined #tryton
2016-01-04 09:51 -!- LordVan(~lordvan@gentoo/developer/LordVan) has joined #tryton
2016-01-04 10:05 -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton
2016-01-04 10:19 -!- tryton-dudas( has joined #tryton
2016-01-04 10:20 -!- gytis( has joined #tryton
2016-01-04 10:32 -!- udono( has joined #tryton
2016-01-04 11:16 -!- leio(~leio@gentoo/developer/leio) has joined #tryton
2016-01-04 11:17 -!- mariomop(~quassel@ has joined #tryton
2016-01-04 11:17 -!- nicoe(~nicoe@2001:6f8:3aa:2:ee55:f9ff:fe7b:f7ac) has joined #tryton
2016-01-04 11:49 -!- mrichez( has joined #tryton
2016-01-04 11:54 -!- tbruyere( has joined #tryton
2016-01-04 12:03 -!- kstenger( has joined #tryton
2016-01-04 12:14 -!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton
2016-01-04 13:26 -!- kstenger1( has joined #tryton
2016-01-04 13:27 -!- kstenger( has joined #tryton
2016-01-04 13:56 -!- smarro(~sebastian@ has joined #tryton
2016-01-04 15:24 -!- bechamel( has joined #tryton
2016-01-04 15:31 -!- lukio( has joined #tryton
2016-01-04 16:08 -!- mariomop( has joined #tryton
2016-01-04 16:27 -!- Nico7878(500f74d0@gateway/web/freenode/ip. has joined #tryton
2016-01-04 16:28 <Nico7878> Hi all! Happy new year to everyone, wish you all a year full of modules devlpt, and bug free!
2016-01-04 16:30 <Nico7878> To begin the new year, I move my sales management to Tryton too. Is there a way to set a manual date on customer purchase order? My lead time is 5 weeks, but usually my customers order product several months ahead. With auto delivery date based on product delivery time, I can't rely on the sales supply module
2016-01-04 17:14 <cedk> Nico7878: I don't understand
2016-01-04 17:14 <cedk> Nico7878: what is "customer purchase order"?
2016-01-04 17:16 <cedk> Nico7878: do you mean, you want to set manually the delivery date on the sale line?
2016-01-04 17:22 <Nico7878> Hello cedk, yes absolutely, I want to set manually the delivery date on the sale line
2016-01-04 17:23 <cedk> Nico7878: you need to customize the sale
2016-01-04 17:23 <cedk> Nico7878: for now, it is a function field but you can define a setter on it
2016-01-04 17:23 <cedk> Nico7878: probably something can be done to be included in base
2016-01-04 17:24 <Nico7878> OK ty, is there an existing module for that? I mean if I have to dive in code I'm affraid my python skills are a bit fresh )
2016-01-04 17:25 <cedk> Nico7878: I'm not aware of
2016-01-04 17:25 <cedk> Nico7878: otherwise, you can still edit the planned date of the moves created on the sale validation
2016-01-04 17:26 <Nico7878> Sounds good to me, I'll try that
2016-01-04 17:27 <Nico7878> I think it would be a rather usefull function to implement in Tryton. In a lot of industries the sale order and the production lead time are in different timeframes
2016-01-04 17:27 <Nico7878> Thank you once again cedk
2016-01-04 17:29 <cedk> Nico7878: indeed I think the common case is the default one of Tryton
2016-01-04 17:29 <cedk> Nico7878: delivery asap
2016-01-04 17:39 <cedk> Nico7878: but I agree that in base we should have the possibility to edit it but following some constraint
2016-01-04 17:40 <Nico7878> yep sure, for instance if you have a lead time, a date that don't break it
2016-01-04 17:41 <cedk> Nico7878: also I think in such case we must store a delta instead of a date probably because if the sale date change
2016-01-04 17:43 <Nico7878> The sale date should be the emission date of the PO, customer side, and it can't be changed. The PO of course could be changed, and you change the sale order accordingly, but a delivery date have to be firm
2016-01-04 17:48 <cedk> Nico7878: I don't understand because you are talking of purchase and sale
2016-01-04 17:50 <Nico7878> I record a sale when I receive a purchase order from my customer. Is it clear like that or do I miss something?
2016-01-04 17:53 <cedk> Nico7878: please avoid mixing naming concept
2016-01-04 17:53 <cedk> Nico7878: in Tryton we always speak from the company point of view otherwise it is impossible to understand
2016-01-04 17:57 <cedk> It is a difficult to know what is a good default behaviour
2016-01-04 17:57 <Nico7878> My apologies, I just wanted to highlight the fact that there's a document that state the sale date, so we can't change it afterward
2016-01-04 17:57 <cedk> because if the sale date change, then the delivery date set could be under the supply delay etc.
2016-01-04 17:58 <cedk> Nico7878: but I don't agree with you about the meaning of the sale date
2016-01-04 17:58 <cedk> Nico7878: the sale date is when the company encode the order, not when the customer request to be
2016-01-04 17:59 <Nico7878> I think we agree on that, we use to encode the sale when we receive the document
2016-01-04 18:02 <cedk> Nico7878: but it can change
2016-01-04 18:02 <cedk> Nico7878: usually the customer will request a quotation and could ask for some change
2016-01-04 18:03 <cedk> Nico7878: then you can update the sale date because it is a new proposal etc.
2016-01-04 18:03 <cedk> also having to edit the delivery date on each line could be to much work
2016-01-04 18:03 <cedk> as usually everything is at the same date
2016-01-04 18:04 <cedk> so probably it should be possible to have a default date on the sale form which could be override per line
2016-01-04 18:04 <Nico7878> In my case unfortunately we have to register sales with different delivery date for each line (
2016-01-04 18:05 <Nico7878> So yes, overriding would be necessary. Anyway I like the idea to have a global date for the default behavior
2016-01-04 18:15 <cedk> Nico7878: you can make a feature request to keep a log if this discussion
2016-01-04 18:34 -!- smarro(~sebastian@ has joined #tryton
2016-01-04 18:47 -!- udono( has joined #tryton
2016-01-04 19:01 -!- smarro(~sebastian@ has joined #tryton
2016-01-04 19:15 <kstenger> is there a shortcut in the client to switch the view from of a one2many field, like the sale lines inside the sale?
2016-01-04 19:18 <kstenger> ctrl+l switches the sale itself, I'd like to switch the lines
2016-01-04 19:18 <cedk> kstenger: no we don't have
2016-01-04 19:19 <kstenger> oh ok!, thank you cedk!
2016-01-04 19:24 -!- tryton-dudas_( has joined #tryton
2016-01-04 19:51 -!- hectorh30(~hectorh30@ has joined #tryton
2016-01-04 20:10 -!- gytis(~gytis@ has joined #tryton
2016-01-04 20:53 -!- bechamel( has joined #tryton
2016-01-04 22:23 -!- lukio( has left #tryton
2016-01-04 22:26 -!- smarro(~sebastian@ has joined #tryton

Generated by 2.17.3 by Marius Gedminas - find it at!