GoZync5

Unzynced Records

GoZync5.UnzyncedRecords History

Hide minor edits - Show changes to output

June 12, 2014, at 03:15 PM by 50.132.85.96 -
Changed lines 3-5 from:
If a user's device is offline, you can't test from the host or server, but you can test inside the scripts you put in their mobile file. In fact, it's pretty common to prevent users from pulling down new records if they have un-synced changes for that table.

When you [[integration | integrated]] GoZync into your file you added a couple fields to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified but not synced the record.
to:
Yes. If a user's device is offline, you can't test from the host or server, but you can test inside the scripts you put in their mobile file. In fact, it's pretty common to prevent users from pulling down new records if they have un-synced changes for that table.

When you [[integration | integrated]] GoZync into your file you added a couple fields to your tables. One of these is "gz_Send"; that field will have a 1 in it if you've modified but not synced the record.
June 30, 2013, at 08:19 PM by 50.132.84.245 -
Added lines 6-7:

Note that the script "Zync - Is a new version permitted" you [[integration | added to your file]] does exactly this, though you'll likely want to extend it to check all the tables in your file.
June 30, 2013, at 08:15 PM by 50.132.84.245 -
Changed lines 1-2 from:
!! How can I test to see if a user has modified by un-synced records on their device?
to:
!! How can I test to see if a user has modified but un-synced records on their device?
Changed line 5 from:
When you [[integration | integrated]] GoZync into your file you added a couple field to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified by not synced the record.
to:
When you [[integration | integrated]] GoZync into your file you added a couple fields to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified but not synced the record.
December 20, 2012, at 12:57 AM by cm - minor edits and clarifications
Changed lines 3-4 from:
Since their device is offline, you can't test from the host or server, but you can test inside the scripts you put in their mobile file. In fact it's pretty common to prevent users from pulling down new records if they have un-synced changes for that table.
to:
If a user's device is offline, you can't test from the host or server, but you can test inside the scripts you put in their mobile file. In fact, it's pretty common to prevent users from pulling down new records if they have un-synced changes for that table.
July 07, 2012, at 02:02 AM by 50.132.84.245 -
Changed lines 1-3 from:
!! How can I tell if I have un-synced records?

When
you [[integration | integrated]] GoZync into your file you added a couple field to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified by not synced the record.
to:
!! How can I test to see if a user has modified by un-synced records on their device?

Since their device is offline, you can't test from the host or server, but you can test inside the scripts you put in their mobile file. In fact it's pretty common to prevent users from pulling down new records if they have un-synced changes for that table.


When you [[integration | integrated]] GoZync into your file you added a couple field to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified by not synced the record.
July 07, 2012, at 12:34 AM by 50.132.84.245 -
Added lines 1-3:
!! How can I tell if I have un-synced records?

When you [[integration | integrated]] GoZync into your file you added a couple field to your primary table occurrence. One of these is "gz_Send"; that field will have a 1 in it if you've modified by not synced the record.
(855) SEEDCODE
[email protected]
Follow us: