I have a change log set up that is not disagreeing with the final information on the OrderHed.TotalMisc field. It’s been on since this record was created, and the most recent change says it was set to 14.4. However, the value in the database is 0.
Can data directives or any other customization circumvent the change log? I was under the impression any change would be logged.
Change Log will catch what fields the corresponding In-Trans Data Directive tells it too. We make one “Change Log” BPM for the table and add all the fields we want tracked.
Note: Change long will no store deletes. So if someone deletes a SO Line any changes will also be deleted. IIRC there is an idea to have change log retain data but I don’t think it’s gotten approved to be implemented yet.
Yes, it is catching some changes to the MiscTotal fields, but it seems to be missing some, because the final total doesn’t agree with the final change.
The tracker is on SO head which has not been deleted - I’m viewing it through the Order Entry UI.
I have see where the sales order total does not change or update. You have may have to close and reoppen the order and lines and releases to see that change. not sure if that is the case here but something i have done in the past.
Hmm, we’re not tracking any of the totals fields on OrderHed. The fields we’re tracking seem to work. Since those are calculated fields, maybe try tracking the OrderMisc table?
We’ve seen issues with calculated fields I think. We don’t track any of the calculated fields on the order and I think it’s because we had issues. We do use a custom BPM to store some calculated values in UD fields. And we have a BPM that logs deletes in a UD table.
And that would make sense… How can it when the logging is on a data directive
Yes, it doesn’t even seem to give the calculated fields as an option.
I tried setting up a data directive on the InvcHead table while tracking a calculation issue in the RMA, and the same thing is happening - the final entry in the log does not match the current value in the database.
Both of these issues started after the most recent update - anyone else experiencing anything like this after the update?