Do you have any third party enhancements that might be interfering?

Also, the field name should be DateUpdated unless you have a UDF or master developer enhancement for the DateLastUpdated field.

Have you actually confirmed the value is not updated using Data File Display and Maintenance?

Thanks David. 

Yes the correct field name is "DateUpdated" on the SO_SalesOrderHistoryHeader.  Sorry about that.

Yes, we have confirmed everything in Data File and Maintenance.

We do have a third party enhancement, but need to do more testing to confirm their work on our SO_SalesOrerHistoryHistory/Detail tables is correct.

In the mean-time we just imported the last two years' worth of data on the SO history headers and changed a non-essential UDF field to a "Y" and then changed them back to a "N".  that triggered the DateUupdated to today's date.  So we've put a bandaid on it and it is working well, and this will be part of our posting process at the end of the day for the short term until we can isolate the issue and get the third party (DSD) to correct it, assuming that's the issue. 

Thanks for your help.

Adam

Thanks David. 

Yes the correct field name is "DateUpdated" on the SO_SalesOrderHistoryHeader.  Sorry about that.

Yes, we have confirmed everything in Data File and Maintenance.

We do have a third party enhancement, but need to do more testing to confirm their work on our SO_SalesOrerHistoryHistory/Detail tables is correct.

In the mean-time we just imported the last two years' worth of data on the SO history headers and changed a non-essential UDF field to a "Y" and then changed them back to a "N".  that triggered the DateUupdated to today's date.  So we've put a bandaid on it and it is working well, and this will be part of our posting process at the end of the day for the short term until we can isolate the issue and get the third party (DSD) to correct it, assuming that's the issue. 

Thanks for your help.

Adam