This is only an issue on our Job Entry/Job Tracker menus.
When initially selecting a job, the change log will track for that job. However, when we enter a new job number, the change log will still be tracking for the previously entered job (see image).
The base application works fine, so it is likely one of our customizations.. But I really am at a loss as to what could be causing this as we have not changed any of the base logic in the menu - only adding things like UD fields. I also cant seem to figure out which events/BOs cause the change log to re-populate. Any suggestions/ideas?
Without knowing your customization details it’s hard to tell. It looks like the method called when you open the change log is Ice.BO.ChgLogSvc/GetChgLog and the only relevant parameter is where you’re opening it from and the actual SysRowID from JobHead:
As for the customization details, the most invasive thing we’ve done on this menu is add some dataviews/events for custom BAQs to pull into some panel grids. Nothing super abnormal.
I am wondering then what causes the sysRowID to update then. I see this event running:
but it still sends the other sysRowID with the payload. Maybe that is stored somewhere else?
Not sure if it’s related, but we have Case 0005266241 (and PRB0270093) about the change logs not sorting by date properly. I was also told to submit an Ideas if we want the PRB fix the bug in 2025.2 (instead of just 2026.1).
