[BUG] MirrorSync 6 Time Stamp being populated.

[Ocean West]

I have a timestamp field on a layout it does not have any auto options - it is used for data and only scripted to indicate a record is expired. 

On initial sync all the blank records now contain 12/31/1969 4:00 PM making navigation invalid as that is part of my test.

Not sure where this is coming from other then MS 

The MS Config does not use this field as a Modification timestamp or any creation timestamp. 

[Ocean West]

It seems to be doing this on OTHER tables in this solution where there is a timestamp (without auto entry options ) being populated with that same date - and subsequent sync will write that date to the hub.

----

Confirmed systemic BUG on a different solution new MS setup created a new field stampTest - Timestamp without  auto entries

On initial sync it gets populated by MS. 

[Ocean West]

made temporary work around by  making the field a text field vs Timestamp