AnsweredAssumed Answered

Scheduled hourly backup may have affected a script execution

Question asked by DomingoUgarte on Oct 22, 2013
Latest reply on Oct 22, 2013 by DomingoUgarte


Scheduled hourly backup may have affected a script execution


     Yesterday we experienced an issue in our time tracking system. I have a FMServer 12 installation conducting hourly backups on the hour from 6am to 8pm. I received a frantic call from one of our data entry personnel responsible for entering and maintaining time. The issue was that somehow someway all the clock-in times for all employees were changed from their original values to 8:10am but only for tickets created from 10/14 until 10/21 (We have data going back as far as January 2013). Under pressure to resolve this. I looked back at the hourly backups starting from the latest 10/21 @ 5pm and went backwards. I found that my 3pm backup had indeed been the last correct backup. Long story short, I exported my primary key field and the clock-in field to an xlsx file, created a new temporary table in my production database, imported those values, created a relationship, and effectively overwrote all 8:10 values to their correct ones. I also noticed that the last modified time value for all the erroneous 8:10am records, values were set to 10/21/2013 3:59:59 PM. This is precisely before backup time. 

     Still with me? Well I have a history table that tracks changes performed on every field modified in my time entry layout. After carefully investigating the event leading to this issue, I noticed that one of the operators, executed this script below precisely at 10/21/2013 3:59:59 PM. It is a button that allows the operator to apply a clock-in time (set from a global time field in my Tickets table) across all the related records in my  EmployeeLines table. Somehow this must be the culprit.

     Is this a bug or is there something I am missing in my script?