Hi Suraj, Deepak,
I agree, I see no reasons why it would be created and not update.
While at it, using currentPromisedDate in services seems also better indeed.
Jacques
Le 08/08/2018 à 11:17, Suraj Khurana a écrit :
Hello Deepak,
This is interesting case. IMO, currentPromisedDate should also be updated
after updating 'Ship Before Date'.
Also, in mentioned services, I propose we should use currentPromisedDate
instead of promisedDateTime field.
--
Best Regards,
Suraj Khurana | Omni-channel OMS Technical Expert
Cell phone: +91 96697-50002
On Tue, Aug 7, 2018 at 11:29 AM, deepak nigam <[email protected]>
wrote:
Hello Devs,
While creating the sales order from the backend, if we set the 'Ship Before
Date' it will be stored in OrderItemShipGroup.shipByDate field and same
will be propagated to OrderItemShipGrpInvRes.promisedDateTime
and OrderItemShipGrpInvRes.currentPromisedDate fields.
On updating the 'Ship Before Date' from the order view page later, the
value gets updated in OrderItemShipGroup entity but remains the same in
OrderItemShipGroupInvRes entity.
Is this the expected behaviour or OrderItemShipGroupInvRes should also get
updated? OrderItemShipGrpInvRes.promisedDateTime &
OrderItemShipGrpInvRes.currentPromisedDate is used in many services like
'getOrderItemShipGroupEstimatedShipDate', 'getItemBackOrderedQuantity',
'reserveProductInventory' etc.
Thanks & Regards
--
Deepak Nigam
