| irc.libera.chat #tryton log beginning Fri Jul 14 12:10:01 AM CEST 2023 | ||
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 22:51 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 22:51 | |
| -!- springwurm(~springwur@2a01:76c0:100:f500:5e89:2ee5:6d38:6030) has joined #tryton | 05:11 | |
| -!- mrichez(~Maxime@2a02:a03f:c2e8:f900:db7c:11fb:1fc6:3112) has joined #tryton | 06:06 | |
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 06:10 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 06:10 | |
| -!- rpit(~rpit@p200300c88f3a900073def768fc0dfae5.dip0.t-ipconnect.de) has joined #tryton | 06:26 | |
| -!- yangoon(~yangoon@pd9eedf81.dip0.t-ipconnect.de) has joined #tryton | 07:26 | |
| -!- rpit(~rpit@p200300c88f3a900073def768fc0dfae5.dip0.t-ipconnect.de) has joined #tryton | 08:29 | |
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 08:56 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 08:56 | |
| mrichez | hi, we are using Supplier shipments for our stocks incoming moves (Purchases will be for the next of our migration). There's something strange when creating a new supplier shipment : i can set a planned date on the first move, then for other moves planned date is readonly | 09:45 |
|---|---|---|
| mrichez | another question about supplier shipment : why when setting a planned date on the shipment , the planned date is not copied on the incoming moves as planned date ? | 09:53 |
| mrichez | for the first question: planned become readonly on the move once you save the shipment. So i you create a new supplier shipment , you can set a planned date on the incoming moves until you save your shipment. | 10:04 |
| cedk | mrichez: planned date can not be set on move when inside a shipment | 10:48 |
| cedk | mrichez: it is the planned date of the shipment that will be set | 10:49 |
| cedk | by _set_move_planned_date | 10:49 |
| cedk | mrichez: for the non readonly when shipment is created, I guess the states should also test _parent_shipment | 10:50 |
| mrichez | cedk: ok for the non readonly. But not sure the _set_move_planned_date is working. I just created a supplier shipment with a planned date in the demo 6.8, there an incoming move, but planned date of incoming move stay empty when saving | 11:07 |
| mrichez | cedk: incoming moves created have no planned date so test : (planned_date or datetime.date.max) < incoming_date is false and planned_date is not written on the move | 11:17 |
| cedk | mrichez: indeed I guess this should be only for move with origin | 11:18 |
| cedk | https://foss.heptapod.net/tryton/tryton/-/commit/fcc64f705f83 | 11:20 |
| cedk | at least we need a way to distinct move created when filling shipment and move that have been created by other document like purchase | 11:22 |
| mrichez | cedk: ok... or if we are the only one concerned by this, i thought about a custo, but it seems difficult to update this code | 11:24 |
| cedk | the change I pointed, did not take into account usage without purchase | 11:25 |
| pokoli | cedk: but with purchase module the move planned date can be also empty, so it will have the same problem. | 11:39 |
| pokoli | I just created a move on the demo using a purchase that does have an empty planned date: https://demo6.8.tryton.org/#demo6.8/model/stock.move/797 | 11:40 |
| cedk | pokoli: no because if it is empty it is because it is computed like that | 11:40 |
| pokoli | As there is a proposal to store the origin planned_date I'm not sure if testing is the latter is really usefull | 11:41 |
| pokoli | I mean: https://foss.heptapod.net/tryton/tryton/-/merge_requests/584 | 11:42 |
| cedk | pokoli: do not unerstand | 11:43 |
| pokoli | I'm wondering if the commit you linked makes sense when the origin planned date is stored | 11:44 |
| cedk | pokoli: it does because it is unrelated | 11:44 |
| pokoli | The user should be able to plan whenever they want, maybe the supplier told them that they will receive the full shipment two days before | 11:44 |
| cedk | pokoli: this is not prevented | 11:46 |
| pokoli | cedk: then I do not understand what the linked commit does. Could you please explain it? | 11:47 |
| pokoli | For example: This shipment https://demo6.8.tryton.org/#demo6.8/model/stock.shipment.in/7 is linked to a move created to a purhcase, I set a planned date on the shipment and it is not replanned | 11:49 |
| cedk | it prevent to change the planned date if it is not for a later date | 11:50 |
| pokoli | cedk: but it does not make sense to prevent that. Something may be planned for a 4 weeks in advance because the supplier initaly had this plan | 11:52 |
| pokoli | But then can be replanned and received in just 3 weeks. So once the suppliers knows they tell you and you update such values in Tryton | 11:53 |
| cedk | pokoli: and this can be done | 11:53 |
| pokoli | cedk: just see the linked shipment. It is not replanned :) | 11:54 |
| -!- springwurm(~springwur@2a01:76c0:100:f500:404:ffb9:f0ca:7671) has joined #tryton | 12:04 | |
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 12:31 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 12:31 | |
| mrichez | another question about Supplier Shipment, does it make sense to have an effective date in the future ? | 13:19 |
| cedk | mrichez: not really except if you can predict the future | 13:21 |
| mrichez | cedk: :-), so it would make sense to prevent to set an effective_date > today ? one of our users made the error.. do i propose as a feature ? | 13:22 |
| cedk | mrichez: a warning about future (like for invoice) could be good | 14:20 |
| mrichez | cedk: ok | 14:24 |
| -!- srgdts(~srgdts@user/srgdts) has joined #tryton | 20:16 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!