Hi guys,
We sometimes experience something similar to https://doc.dynamicweb.com/forum/dynamicweb-9-0-upgrade-issues/dynamicweb-9-0-upgrade-issues/custom-order-field-of-type-datetime-is-getting-flushed-by-dw .
We use this Text(20) custom order field to store if an order is of type buy or rent.
This value is set ONLY ONCE (on the add to cart action) and from there on it is being read only.
It is used as input for the price provider, to which payment provider is being redirected, which information is asked to the customer, which communication is sent to the customer, etc.
So this is a very very very important value for us ...
Now we notice that SOMETIMES, and we suspect when the user is going back and forwards using the browser button in the checkout process moving from the website to payment provider and back, the value of this orderfield gets flushed.
We think the system creates new rows in the EcomOrder table or something due to state changes when the flush happens, but can't really put a finger on it to prevent this to happen on our side (if that is even possible).
This is a big problem for us, because once this value is gone, the order can't be finished anymore.
I just think Dw should NEVER flush a custom field value.
Is there anything you can do for us, or do you have any idea what could cause this to happen?
This is directly affecting the sales ....