GoZync5

Time Zones

GoZync5.TimeZones History

Hide minor edits - Show changes to output

August 06, 2018, at 09:30 PM by 192.88.134.15 -
Changed line 5 from:
'''Note: As of version 5.09, this method is no longer necessary.'''
to:
'''Note: As of version 5.09, the following modification is no longer necessary.'''
June 14, 2017, at 11:57 PM by KC Embrey - Added note that this is not necessary as of version 5.09
Added lines 4-5:

'''Note: As of version 5.09, this method is no longer necessary.'''
June 12, 2014, at 02:43 PM by 50.132.85.96 -
Changed line 3 from:
Irrespective of time zones, GoZync maintains the last sync time on the server. We're not picking winners based on when a field was edited: it's last sync wins. Which is usually perfect since a) the whole point of GoZync is to give mobile users only *their* records, and b) you have the option of syncing only the fields that have changed so you don't have whole records colliding. (You can read about how we handle conflicts [[Conflicts | here]].)
to:
Irrespective of time zones, GoZync maintains the last sync time on the server. We're not picking winners based on when a field was edited; instead, it's last sync wins. Which is usually perfect since a) the whole point of GoZync is to give mobile users only *their* records, and b) you have the option of syncing only the fields that have changed so you don't have whole records colliding. (You can read about how we handle conflicts and learn about locking checked-out records [[Conflicts | here]].)
December 19, 2012, at 11:58 PM by cm - minor edits and clarifications
Changed lines 3-6 from:
Time zones are only handled in so far as we maintain the last sync time on the server. We're not picking winners based on when a field was edited, it's last sync wins. Which is usually perfect since a) the whole point of GoZync is to give mobile users only *their* records, and b) you have the option of syncing only the fields that have changed so you don't have whole records colliding. (You can read about how we handle conflicts [[Conflicts | here]].)

However, if you have users in times zones different from the server's time zone
, you will want to make one change to the stock GoZync integration in order to make sure your users get all the changes since their last sync.
to:
Irrespective of time zones, GoZync maintains the last sync time on the server. We're not picking winners based on when a field was edited: it's last sync wins. Which is usually perfect since a) the whole point of GoZync is to give mobile users only *their* records, and b) you have the option of syncing only the fields that have changed so you don't have whole records colliding. (You can read about how we handle conflicts [[Conflicts | here]].)

However, if you have users in different time zones than the server,
you will want to make one change to the stock GoZync integration in order to make sure your users get all the changes since their last sync.
Changed line 15 from:
This mod will tell GoZync to store the record's change times according to the server time, which is in line with how we maintain the device's last sync time.
to:
This mod will tell GoZync to store the record's change times according to the server time, which is in line with how we maintain the device's last sync time.
November 12, 2012, at 05:46 AM by 50.132.84.245 -
Changed lines 7-8 from:
-> 1. Duplicate the field gz_ModTimeStamp and name the new instance gz_ModTimeStampFeeder
to:
-> 1. Edit your hosted file and duplicate the field gz_ModTimeStamp and name the new instance gz_ModTimeStampFeeder
November 12, 2012, at 03:48 AM by 50.132.84.245 -
Added lines 1-15:
!! How does GoZync deal with time zones?

Time zones are only handled in so far as we maintain the last sync time on the server. We're not picking winners based on when a field was edited, it's last sync wins. Which is usually perfect since a) the whole point of GoZync is to give mobile users only *their* records, and b) you have the option of syncing only the fields that have changed so you don't have whole records colliding. (You can read about how we handle conflicts [[Conflicts | here]].)

However, if you have users in times zones different from the server's time zone, you will want to make one change to the stock GoZync integration in order to make sure your users get all the changes since their last sync.

-> 1. Duplicate the field gz_ModTimeStamp and name the new instance gz_ModTimeStampFeeder

-> 2. Edit the original instance of gz_ModTimeStamp and make it an auto enter calc, returning the type "timestamp" with the following definition:

--> If ( gz_ModTimeStampFeeder ; Get ( CurrentHostTimestamp ) )

-> Be sure to UNcheck "Do not replace existing value...". You'll need to alter this timestamp field in each of the tables in your hosted file.

This mod will tell GoZync to store the record's change times according to the server time, which is in line with how we maintain the device's last sync time.
(855) SEEDCODE
support@seedcode.com
Follow us: