4 Replies Latest reply on Mar 27, 2015 7:45 AM by Fred(CH)

    Record MODIFICATION auto-enter : Date, Time, etc...

    Fred(CH)

      Summary

      Record MODIFICATION auto-enter : Date, Time, etc...

      Product

      FileMaker Pro

      Version

      13.0v5 (and probably all priors)

      Operating system version

      Irrelevant but OS X 10.8.5

      Description of the issue

      When using a record modification auto enter option, the field is defined even the record never was modified stricto sensu. So, for a timestamp for instance, you will get the current timestamp where the record were committed the first time instead of an empty field.

      Steps to reproduce the problem

      1. Create a file with one table and two fields : "Name" (text) and "Modification" (timestamp).
      2. On the second, set a record modification auto enter option.
      3. Create a new blank record without entering nothing
      4. Commit the blank record

      Expected result

      The timestamp must be empty, since the record has never been modified in any way.

      Actual result

      3. -- > the value is set using the timestamp when the new record were created (note the Get (OpenRecordState) returns 1, since it never was committed even one time)

      4. -- > the value is then set using the timestamp when the new record were firstly committed.

      I assume the bug is essentially on 3. Then the behavior on 4. is probably a consequence.

      Exact text of any error message(s) that appear

      N/A

      Configuration information

      N/A

      Workaround

      Don't use any auto-enter for modification, and use rather a OnRecordCommit script trigger to set your modification field. But keep in mind that a script trigger is layout level so it very touchy and probably unreliable in most databases. Think also to patch all Importation, Replace and Lookup Commands etc… Ouch… this one is SEVERE.