Question1Replies141Views×Close popoverChunzhi Hong (Chunzhi_Hong) PEGA Consulting Manager, Pega Consulting Pegasystems Inc. JP View Profile Chunzhi_Hong Member since 2013 138 posts PEGA Posted: June 28, 2016Last activity: June 28, 2016Posted: 28 Jun 2016 4:58 EDTLast activity: 28 Jun 2016 21:56 EDT Closed Solved 7.2 pyResolvedTimeStamp is missing if work object is restored from archived zip file created by PurgeArchive toolI found that pyResolvedTimeStamp is missing if work object is restored from archived zip file which is created by PurgeArchive tool.Is this intended behavior or is this a potential defect of PurgeArchive tool ?If pyResolvedTimeStamp is not exported, what's the purpose for this behavior? Case Management Data Integration System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 4 years agoPosted: 28 Jun 2016 21:56 EDT×Close popoverChunzhi Hong (Chunzhi_Hong) PEGA Consulting Manager, Pega Consulting Pegasystems Inc. JP View ProfileChunzhi_Hong PEGA replied to Chunzhi_HongIt turns out that the work object doesn't have pyResolvedTimeStamp value from the beginning due to the application bug.However, the exposed column pyResolvedTimeStamp was updated manually before running PurgeArchive tool, so the work object without pyResolvedTimeStamp in the BLOB also included in the archive file.