c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #10589
[Bug 696793] [NEW] [6.0] Purchase expected date wrong value
Public bug reported:
Create a purchase order, create two lines with two different products
and don't define an expected date on the PO.
1st line : Scheduled date = 01/23/2011
2nd line : Scheduled date = 01/23/2011
If you save the PO, the expected date of the PO is today and the
scheduled date of two lines is also today whereas it should be
01/13/2011.
After that, if you remove the expected date on the PO, change the
scheduled date on lines with the value defined above and save the PO,
values are ok.
Values should be ok at the first saving time.
** Affects: openobject-addons
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/696793
Title:
[6.0] Purchase expected date wrong value
Status in OpenObject Addons Modules:
New
Bug description:
Create a purchase order, create two lines with two different products and don't define an expected date on the PO.
1st line : Scheduled date = 01/23/2011
2nd line : Scheduled date = 01/23/2011
If you save the PO, the expected date of the PO is today and the scheduled date of two lines is also today whereas it should be 01/13/2011.
After that, if you remove the expected date on the PO, change the scheduled date on lines with the value defined above and save the PO, values are ok.
Values should be ok at the first saving time.
Follow ups
-
[Bug 696793] Re: [6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)
From: Xavier (Open ERP), 2011-05-26
-
[Bug 696793] Re: [6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)
From: Mohammed Shekha(Open ERP), 2011-05-18
-
[Bug 696793] Re: [6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)
From: Mohammed Shekha(Open ERP), 2011-05-18
-
[Bug 696793] Re: [6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)
From: Launchpad Bug Tracker, 2011-05-18
-
[Bug 696793] Re: [6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)
From: Jiten (OpenERP), 2011-04-04
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jiten (OpenERP), 2011-01-27
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Harry (OpenERP), 2011-01-18
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Harry (OpenERP), 2011-01-18
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Harry (OpenERP), 2011-01-18
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Launchpad Bug Tracker, 2011-01-18
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Antony Lesuisse, 2011-01-13
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jas(OpenERP), 2011-01-06
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: qdp (OpenERP), 2011-01-06
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: qdp (OpenERP), 2011-01-06
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jra (Open ERP), 2011-01-06
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jra (Open ERP), 2011-01-05
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jas(OpenERP), 2011-01-04
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Quentin THEURET, 2011-01-04
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jas(OpenERP), 2011-01-04
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Jas(OpenERP), 2011-01-04
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Quentin THEURET, 2011-01-03
-
[Bug 696793] Re: [6.0] Purchase expected date wrong value
From: Launchpad Bug Tracker, 2011-01-03
-
[Bug 696793] [NEW] [6.0] Purchase expected date wrong value
From: Quentin THEURET, 2011-01-03
References