Date Formats
GoZync3.DateFormats History
Hide minor edits - Show changes to markup
- First off, as of version 3.16, GoZync recreates the interface and value list records it needs when a newly created clone is opened. So we strongly recommend you implement the changes before making your clones.
- First off, as of version 3.16, GoZync recreates the interface and value list records it needs when a newly created clone is opened. So we strongly recommend you implement the changes in the latest version of GoZync before making your clones.
Dates don't seem to be zyncing correctly, but text fields are. What's going on?
The scripts in GoZync represent all your data as "text" in the document we pass back and forth. Converting dates to and from text is the only place where FileMaker fails to respect "Use System Formats". In these cases FM uses the date format initialized when the file was created: if your file was created with UK dates, for example, it will conflict with GoZyncs file which were created with US dates.
Fortunately this is easy to fix. Cloning a file (Save a Copy As / Clone) wipes this date information and resets it using the format of the machine which next opens the file. So making a clone of GoZyncHosted and GoZyncMobile should get you sorted. (If you're using one of our mobile files like "QuickContact" you'll want to clone that as well.)
If you only have a few dates you could also simply intercept our SetField steps for those fields and force the dates into your format with FileMaker's date function. But cloning is a system-wide fix and will apply to any new date fields you add to your solution later.
Dates don't seem to be Zyncing correctly, but text fields are. What's going on?
The scripts in GoZync represent all your data as "text" in the document we pass back and forth. Converting dates to and from text is the only place where FileMaker fails to respect "Use System Formats". In these cases FM uses the date format initialized when the file was created. If your file was created with UK dates, for example, it will conflict with GoZync's file, which was created with US dates.
Fortunately, this is easy to fix. Cloning a file (Save a Copy As / Clone) wipes this date information and resets it using the format of the machine that next opens the file. So making a clone of GoZyncHosted and GoZyncMobile should get you sorted. (If you're using one of our mobile files like "QuickContact" you'll want to clone that as well.)
If you only have a few dates you could also simply intercept our SetField steps for those fields and force the dates into your format with FileMaker's date function. But cloning is a system-wide fix, and will apply to any new date fields you add to your solution later.
- If you're already hosting GoZync pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources. If it's been a while since you had GoZync off your server, you may have forgotten how to get it syncing in Pro on one machine, read "Playing with GoZync in FileMaker Pro" here.
- If you're already hosting GoZync, pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources. If it's been a while since you had GoZync off your server, you may have forgotten how to get it syncing in Pro on one machine, read "Playing with GoZync in FileMaker Pro" here.
- Next, cloning will erase the integration information you entered into GoZyncHosted. That's not as bad as it sounds since most of the work of integrating is adding the layouts and table occurrences: all that will remain. All you'll have to do is add the dashboard records for each main layout you're syncing and fill out the first tab of the integration instructions for each layout.*
- Next, cloning will erase the integration information you entered into GoZyncHosted. That's not as bad as it sounds, since most of the work of integrating is adding the layouts and table occurrences. All you'll have to do is add the dashboard records for each main layout you're syncing and fill out the first tab of the integration instructions for each layout.*
- If you're already hosting GoZync pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources. If it's been a while since you had GoZync off your server, you may have forgotten how to get it syncing in Pro on one machine, read "fdadf" here.
- If you're already hosting GoZync pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources. If it's been a while since you had GoZync off your server, you may have forgotten how to get it syncing in Pro on one machine, read "Playing with GoZync in FileMaker Pro" here.
- If you're already hosting GoZync pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources
- If you're already hosting GoZync pull it off your server and do this work locally. Test the sync at least once to make sure you're syncing locally (with all files on one computer) again, especially if you changed your External Data Sources. If it's been a while since you had GoZync off your server, you may have forgotten how to get it syncing in Pro on one machine, read "fdadf" here.
Fortunately this is easy to fix. Cloning a file (Save a Copy As / Clone) wipes this date information and resets it using the format of the machine which next opens the file.
So making a clone of GoZyncHosted and GoZyncMobile (if you're using ours) should get you sorted. There is data in both files you'll still need, however. So after cloning, renaming, and opening you're new files, you'll want to import data from the uncloned versions into all the tables in both files.
If you only have a few dates you could also simply intercept our SetField steps for those fields and force the dates into your format with FileMaker's date function.
Fortunately this is easy to fix. Cloning a file (Save a Copy As / Clone) wipes this date information and resets it using the format of the machine which next opens the file. So making a clone of GoZyncHosted and GoZyncMobile should get you sorted. (If you're using one of our mobile files like "QuickContact" you'll want to clone that as well.)
If you only have a few dates you could also simply intercept our SetField steps for those fields and force the dates into your format with FileMaker's date function. But cloning is a system-wide fix and will apply to any new date fields you add to your solution later.
How to make a clone GoZync
This isn't hard, but like many things in FileMaker, it helps to do things in order.
That's it.
If you only have a few dates you could also simply intercept our SetField steps? for those fields and force the dates into your format with FileMaker's date function.
If you only have a few dates you could also simply intercept our SetField steps for those fields and force the dates into your format with FileMaker's date function.
So making a clone of GoZyncConnector and Mobile (if you're using ours) should get you sorted. There is data in both files you'll still need, however. So after cloning, renaming, and opening you're new files, you'll want to import data from the uncloned versions into the following tables:
GoZyncConnector: GoZync and Interface Mobile: PortalRows, GoZync, and Interface
That's it.
So making a clone of GoZyncHosted and GoZyncMobile (if you're using ours) should get you sorted. There is data in both files you'll still need, however. So after cloning, renaming, and opening you're new files, you'll want to import data from the uncloned versions into all the tables in both files.
If you only have a few dates you could also simply intercept our SetField steps? for those fields and force the dates into your format with FileMaker's date function.
Dates don't seem to be zyncing correctly, but text fields are. What's going on?
The scripts in GoZync represent all your data as "text" in the document we pass back and forth. Converting dates to and from text is the only place where FileMaker fails to respect "Use System Formats". In these cases FM uses the date format initialized when the file was created: if your file was created with UK dates, for example, it will conflict with GoZyncs file which were created with US dates.
Fortunately this is easy to fix. Cloning a file (Save a Copy As / Clone) wipes this date information and resets it using the format of the machine which next opens the file.
So making a clone of GoZyncConnector and Mobile (if you're using ours) should get you sorted. There is data in both files you'll still need, however. So after cloning, renaming, and opening you're new files, you'll want to import data from the uncloned versions into the following tables:
GoZyncConnector: GoZync and Interface Mobile: PortalRows, GoZync, and Interface
That's it.