SG-1356 Datalake - Data Correction script to update lastsaved date for records that did not sync to Datalake. - HxGN EAM - Version 12.0 - Hexagon

HxGN EAM Resolved Issues for 2022

Language
English
Product
HxGN EAM
Search by Category
HxGN EAM Version
12

SG-1356 Datalake - Data Correction script to update lastsaved date for records that did not sync to Datalake.

 Description 

Customer has a number of records from R5BOOKEDOURS that was not picked up to sync to Datalake. As documented in previous Jira EAM-55695, In some instances, for highly transactions tables data sometimes does not sync to Datalake. In these instances one solution is on the Datalake schedule, update the lastupdated date back to prior date so records will be picked up again. The other solution would be that the records needs to be “touched†to update the lastsaved date in order for the record to be picked up again. Resetting the scheduled last updated date back to an older date is a issue as data that previously synced successfully will synced again, which will cause duplicate records. As these are R5BOOKEDHOURS records, these records cannot be updated via the frontend. Request data correction script to update affected records so they will be picked up to sync to Data Lake.