[6.0] [Trunk] Purchase expected date wrong value (function field 'fnct_inv' does not work properly in web client)

[Quentin THEURET @Amaris]

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/13/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.

[Jamin Shah(OpenERP) (jamin-openerp)]

Hello Quentin,

I have tested your scenario,but it's working as expected.
Would you please check again and notify me?

I have attached screen-shot for your reference.

Thanks.

[Quentin THEURET @Amaris (qtheuret)]

Hello Jas,

On GTK, the behaviour is good.
It seems that the problem occurs only on Web client because when you create a new PO line, the PO is saved with the date of today as expected date.

On my patch, I remove the computation of expected date if no lines. The expected date isn't a mandatory field, so, if no lines, the PO doesn't need expected date.

I have attached screen-shots for your reference.

Thanks.

[Jiten (OpenERP) (jiten-openerp)]

Hello,

I have transfered this issue to addons because, i have found that When user try to modify schedule date from purchase order line than first time its modified successfully, but when user save the purchase order than its changed (update - set) by method "_set_minimum_planned_date" of purchase order.
i confirmed it with addons team.

and suggested solution also need to merge ( https://code.launchpad.net/~tempo-openerp/openobject-addons/trunk-bugfix-696793/+merge/45035 )

Please check this issue in purchase.py - line number 66 to 89.
check the value with po.minimum_planned_date.

Thanks.

[qdp (OpenERP) (qdp)]

the merge proposal is rejected. This should definitelly be fixed in the web client.

[Harry (OpenERP) (hmo-tinyerp)]

Hello,

I confirmed this bug into web-client. expected date of the PO is a function field which are calculated base on scheduling date of PO lines. After change of Schedule date of any PO line, expected date of PO is not updated. Web client is sent request to call calculation of expected date but On Save, web client is not consider this new expected date.

Thanks

[Jiten (OpenERP) (jiten-openerp)]

Hello,

After change of Schedule date of any PO line, expected date of PO is correctly set by "_minimum_planned_date" but its Re-set by "_set_minimum_planned_date" and I found that "_set_minimum_planned_date" works correctly if user changes the expected date by PO only. When user changes the date by PO line then its not working.

WEB client passes all correct fields and values.
GTK works fine because when we change it by PO line and save by final PO then function field is not being passed to server. And that is different structure from WEB.

Correct me if I misunderstood.
Thanks.

[Mohammed Shekha(Open ERP) (msh-openerp)]

Hello All,

 The fix for web-client has been committed to
lp:~openerp-dev/openobject-client-web/6.0-opw-4834-msh with the following revision.

Revision-info:
4607 : <email address hidden>
Soon it will be merged into trunk web-client.

Thanks for your patience and co-operation.