Object Modification Date when applying ESU or ASU

karryd

karryd

Active Member
Hi,

Has anyone noticed a situation where the modification dates of objects are set to the current date in OMW when an ESU or ASU is applied?
We have noticed that when we apply an ESU or ASU with the workbench or Change Assistant (2.5), the date the objects show being modified is the date the ESU was applied to the path code. From what I know of ESU and ASU installs, you should be able to apply the update to DV811, then retrofit, then apply the update to PY811, then promote your retrofits. In this case, the objects in our UJ3(Update 2) retrofit projects were not promoted from DV811 to PY811 because OMW thought the objects applied from UJ3 into PY811 were the most recent as they had a modification date the same as the date we applied the UJ3 to PY811. We had to demote the retrofit projects back to DV811, do a check in/out to reset the last modified date, and then re-promote in order to get our retrofits into the PY811 path code.
After an ESU or ASU install, we can see the date of the ASU install in the F9861 and F9860 SIDM field which is where the last modified date of the object should be.
We are currently at E1 8.11 SP1 8.97.3.1, going to Update 2.
Thanks!

Karry
 
Back
Top