Hi there,
Using the data integration framework we imported ledgers into the EcomOrders table. Now when editing and saving a ledger in the backend, we get the attached "SqlDateTime Overflow" exception.
After some debugging and data manipulation, it turns out the issue is with the column OrderPriceCalculation . In the database this column is nullable and we didn't supply a value for it during import. However, when this value remains null, saving a ledger causes the code to crash. We can work around it by assigning a value to that column on all ledgers in the backend.
Did this change recently? We never had to do this in the past. I can see some recent changes in the code from a DateTime to a Date that may be related? Maybe it now no longer sends DBNull.Value but DateTime.MinValue or so instead?
Since OrderPriceCalculation doesn't make sense for a ledger item, I would like this field to remain nullable. Can you look into this please?
Thanks!
Imar
