GoZync4

Troubleshooting

GoZync4.Troubleshooting History

Hide minor edits - Show changes to output

October 09, 2015, at 03:50 PM by John posted by Dan - Added Server Authentication Error section
Changed lines 42-46 from:
-> Or one of your layouts is unable to be read by FileMaker (this is a FMP bug short of corruption). For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error, delete that sync layout in GoZyncMobile and recreate it.
to:
-> Or one of your layouts is unable to be read by FileMaker (this is a FMP bug short of corruption). For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error, delete that sync layout in GoZyncMobile and recreate it.

!! Authentication Errors in Server Logs

-> This isn't actually an error: FileMaker Server is just a little too verbose in its logging, and while many people have asked FileMaker to change this, it's been around for a while. What's happening is that the user has other files in the set up that open with "Admin" as the account name. When one of those files calls a script in GoZyncLicense, FileMaker tries to open GoZyncLicense using the same credentials--tries to pass that authentication into the related files. This is a great feature of FileMaker, but in our case, GoZyncLicense doesn't have an Admin account. So, the attempt fails--and FileMaker Server logs the "error" even though the user never sees it. FileMaker then tries the "On Opening" account setup in GoZyncLicense hosted and the solution opens right up. You'll see the same error in FileMaker Server any time two files in solution don't share the logged in account or password. It's not an error and we all wish it wouldn't show up in the log
.
August 28, 2015, at 05:26 PM by 142.4.217.188 -
Added lines 14-15:

-> Another cause could be that the field's name begins with a numeral or period, has the same name as a FileMaker function, or contains the word "or", "and" or "not", or a symbol that's being interpreted as an operator.
July 06, 2014, at 02:29 PM by 50.132.85.96 -
Changed line 29 from:
-> FileMaker Go13 takes a bit longer to close files than Go12 did so you may need to increase the time GoZync waits for your file to close before replacing it. Instructions for changing this are [[http://www.seedcode.com/support/viewtopic.php?f=38&t=4017 | ]] here. If the 1 second delay mentioned there doesn't work, add 4 seconds and see if that gets it. Then back down to 3 or 2 seconds to find the time that works for your file.
to:
-> FileMaker Go13 takes a bit longer to close files than Go12 did so you may need to increase the time GoZync waits for your file to close before replacing it. Instructions for changing this are [[http://www.seedcode.com/support/viewtopic.php?f=38&t=4017 | here]]. If the 1 second delay mentioned there doesn't work, add 4 seconds and see if that gets it. Then back down to 3 or 2 seconds to find the time that works for your file.
July 06, 2014, at 02:27 PM by 50.132.85.96 -
Changed line 27 from:
File is Locked or In Use when pulling down a new version
to:
'''File is Locked or In Use when pulling down a new version'''
July 06, 2014, at 02:27 PM by 50.132.85.96 -
Added lines 27-29:
File is Locked or In Use when pulling down a new version

-> FileMaker Go13 takes a bit longer to close files than Go12 did so you may need to increase the time GoZync waits for your file to close before replacing it. Instructions for changing this are [[http://www.seedcode.com/support/viewtopic.php?f=38&t=4017 | ]] here. If the 1 second delay mentioned there doesn't work, add 4 seconds and see if that gets it. Then back down to 3 or 2 seconds to find the time that works for your file.
April 07, 2014, at 11:41 PM by 50.132.84.245 -
Added lines 22-25:

'''One of my tables has a generic sync error'''

-> Check to make sure you have values in the UUID field this table is pulling from.
October 12, 2013, at 12:09 AM by 50.132.84.245 -
Changed lines 3-4 from:
'''Nothing works.'''
to:
'''Nothing works or Can't Connect.'''
Changed line 7 from:
-> If that doesn't help it is likely your file references (External Data Sources): more on checking those [[ExternalDataSources | here]].
to:
-> If that doesn't help, or you can't connect, it is likely your file references (External Data Sources): more on checking those [[ExternalDataSources | here]].
June 30, 2013, at 08:14 PM by 50.132.84.245 -
Changed lines 27-28 from:
Pretty rare, but if you're seeing this message it can be caused by one of three things:
to:
Pretty rare, but if you're seeing this message it can be caused by one of four things:
Changed lines 33-35 from:
-> Some of your field, layout, or table occurrence names include prohibited characters (!/~;&# etc) This is the most likely reason.

-> Or
one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)
to:
-> Or one of your layouts is unable to be read by FileMaker (this is a FMP bug short of corruption). For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error, delete that sync layout in GoZyncMobile and recreate it.
June 30, 2013, at 08:11 PM by 50.132.84.245 -
Deleted lines 10-11:
-> If you're not seeing records pushed up from Mobile to Hosted, the records could be ending up in GoZyncHosted's inbox and simply have processing errors (field name mismatch, etc.) check the GoZycHosted inbox to see if they are there.
Changed lines 19-20 from:
-> It could also be that your related table uses a relationship ''not'' based on the primary key of the parent's record table. Related tables to be synced ''must'' be related to the primary key of their parent record. More complex relationships should be synced as their own layouts.
to:
-> It could also be that your related table uses a relationship ''not'' based on the primary key of the parent's record table. Related tables to be synced ''must'' be related to the primary key of their parent record. More complex relationships should be synced as their own tables.
June 30, 2013, at 08:11 PM by 50.132.84.245 -
June 30, 2013, at 08:11 PM by 50.132.84.245 -
Changed lines 9-10 from:
-> You'll also want to make sure that the mobile users are authenticated into your hosted solution (via GoZyncHosted) with a privilege set that lets them edit records. If all that sounds like stuff you've never heard of, this likely isn't your problem. This only comes up when folks have more elaborate security set ups.
to:
-> You'll also want to make sure that the mobile users are authenticated into your hosted solution with a privilege set that lets them edit records. If all that sounds like stuff you've never heard of, this likely isn't your problem. This only comes up when folks have more elaborate security set ups.
June 26, 2013, at 06:37 PM by 108.38.141.66 -
Deleted lines 24-29:
'''Other things to check...'''

-> The sync layouts in your files can not have script triggers on them.

-> Visit the integration again in GoZyncHosted and click through the tabs for each table: tabs like "Field and Scripts" will run checks to make sure you don't have bad field names.

June 26, 2013, at 06:37 PM by 108.38.141.66 -
Changed lines 19-24 from:
-> This is either because the related fields aren't on your sync layout, or that you haven't actually [[TriggeringRecordMods | triggered a modification in the parent record]].

-> It could also be that
the portals on your sync layout use a relationship ''not'' based on the primary key of the layout's table. Portal data to be synced must be related to the primary key of the table the portal is on. More complex relationships should be synced as their own layouts.

-> Finally, we've seen a few cases where
the relationship used if your solution is based on fields X and Y where the graph you wired up in GoZyncMobile uses a field than X for the primary key in your table. Double check that what your solution uses as the primary key for a relationship is the same field you use as a primary key in the graphs of GoZyncMobile and GoZyncHosted.
to:
-> This could be because you haven't actually [[TriggeringRecordMods | triggered a modification in the parent record]].

-> It could also be that your related table uses a relationship ''not'' based on
the primary key of the parent's record table. Related tables to be synced ''must'' be related to the primary key of their parent record. More complex relationships should be synced as their own layouts.

-> Finally, you may have specified the wrong field or table when filling out the "required" column on
the configuration tab of GoZyncHosted, so double check that.
June 26, 2013, at 06:11 PM by 108.38.141.66 -
Changed lines 31-32 from:
(:incude ErrorCodes:)
to:
(:include ErrorCodes:)
June 26, 2013, at 06:10 PM by 108.38.141.66 -
Changed lines 31-32 from:
to:
(:incude ErrorCodes:)
June 26, 2013, at 06:02 PM by 108.38.141.66 -
Changed lines 15-20 from:
-> The most common cause of unexpected sync behavior is that you're not syncing the layout you think you are. Remember, GoZync syncs the fields on your sync layout so visit the Integration in GoZyncHosted and make sure the layouts you've specified there are the ones you want to use.

-> Want to look closer? Turn off Field Level Merge in [[Zync Options]] and perform a sync for the table in question. Now visit the InBox in GoZyncHosted and export the last package: you'll see the fields being synced at the beginning of the package. If the fields you want to sync aren't there, they aren't on your sync layout in your mobile file.

-> Remember, you'll only see a package in InBox if you push or round-trip, to see pull packages, look at the Zync Logs tab in GoZyncMobile for the last package processed: that will show you the fields on your hosted zync layout
.
to:
-> The most common cause of unexpected sync behavior is that you're not syncing the layout you think you are. Remember, GoZync syncs the fields on your sync layout so visit the configuration tab in GoZyncHosted and make sure the layouts you've specified there are the ones you want to use.
June 26, 2013, at 06:00 PM by 108.38.141.66 -
Changed lines 5-8 from:
-> The most common issue when setting up as sync is that records appear not to sync but are simply waiting in the GoZyncHosted InBox to be processed. This could be because of a field mapping error, or simply because you only "pushed" and didn't do a round trip. You can learn more about how to automate inbox processing here: [[inbox processing]].

-> If the integration
checks out with green check marks but you get NO sync action, try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.
to:
-> If the configuration checks out with green check marks but you get NO sync action, try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.
June 26, 2013, at 06:00 PM by 108.38.141.66 -
Deleted lines 22-23:
-> For more on processing the inbox in GoZyncHosted, see [[processing errors]].
June 26, 2013, at 06:00 PM by 108.38.141.66 -
Deleted lines 0-3:
!! Processing the inbox

For errors processing the inbox in GoZyncHosted, see [[processing errors]].

June 09, 2013, at 06:38 PM by 50.132.84.245 -
Changed lines 13-14 from:
-> If that doesn't help it is likely your file references (Data Sources): more on checking those [[ExternalDataSources | here]].
to:
-> If that doesn't help it is likely your file references (External Data Sources): more on checking those [[ExternalDataSources | here]].
June 09, 2013, at 06:37 PM by 50.132.84.245 -
Deleted line 4:
Added lines 9-10:
-> The most common issue when setting up as sync is that records appear not to sync but are simply waiting in the GoZyncHosted InBox to be processed. This could be because of a field mapping error, or simply because you only "pushed" and didn't do a round trip. You can learn more about how to automate inbox processing here: [[inbox processing]].
June 09, 2013, at 06:35 PM by 50.132.84.245 -
Changed lines 5-16 from:
!! License Violation Detected

Pretty rare, but if you're seeing this message it can be caused by one of three things:

-> You're syncing more than your license allows.

-> You're trying to call some of the GoZync sub scripts without including our license file (unlikely, unless you're trying to bypass the license).

-> Some of your field, layout, or table occurrence names include prohibited characters (!/~;&# etc) This is the most likely reason.

-> Or one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)

to:
Changed lines 40-53 from:
-> Visit the integration again in GoZyncHosted and click through the tabs for each table: tabs like "Field and Scripts" will run checks to make sure you don't have bad field names.
to:
-> Visit the integration again in GoZyncHosted and click through the tabs for each table: tabs like "Field and Scripts" will run checks to make sure you don't have bad field names.


!! License Violation Detected

Pretty rare, but if you're seeing this message it can be caused by one of three things:

-> You're syncing more than your license allows.

-> You're trying to call some of the GoZync sub scripts without including our license file (unlikely, unless you're trying to bypass the license).

-> Some of your field, layout, or table occurrence names include prohibited characters (!/~;&# etc) This is the most likely reason.

-> Or one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)
April 05, 2013, at 03:40 PM by 50.132.84.245 -
Changed lines 13-14 from:
-> Some of your field, layout, or table occurrence names include prohibited characters (!~;&# etc) This is the most likely reason.
to:
-> Some of your field, layout, or table occurrence names include prohibited characters (!/~;&# etc) This is the most likely reason.
April 05, 2013, at 03:26 PM by 50.132.84.245 -
Added lines 37-38:
-> For more on processing the inbox in GoZyncHosted, see [[processing errors]].
March 02, 2013, at 11:52 PM by 67.23.193.215 -
Added lines 43-44:
-> Finally, we've seen a few cases where the relationship used if your solution is based on fields X and Y where the graph you wired up in GoZyncMobile uses a field than X for the primary key in your table. Double check that what your solution uses as the primary key for a relationship is the same field you use as a primary key in the graphs of GoZyncMobile and GoZyncHosted.
Added lines 9-10:
-> You're syncing more than your license allows.
February 07, 2013, at 02:36 PM by 50.132.84.245 -
Added lines 25-26:
-> If you're not seeing records pushed up from Mobile to Hosted, the records could be ending up in GoZyncHosted's inbox and simply have processing errors (field name mismatch, etc.) check the GoZycHosted inbox to see if they are there.
Changed lines 31-34 from:
-> Want to look closer? Turn of Field Level Merge in [[Zync Options]] and perform a sync for the table in question. Now visit the InBox in GoZyncHosted and export the last package: you'll see the fields being synced at the beginning of the package. If the fields you want to sync aren't there, they aren't on your sync layout in your mobile file.

-> Remember, you'll only see a package in InBox if you pus or round-trip, to see pull packages, look at the Zync Logs tab in GoZyncMobile for the last package processed: that will show you the fields on your hosted zync layout.
to:
-> Want to look closer? Turn off Field Level Merge in [[Zync Options]] and perform a sync for the table in question. Now visit the InBox in GoZyncHosted and export the last package: you'll see the fields being synced at the beginning of the package. If the fields you want to sync aren't there, they aren't on your sync layout in your mobile file.

-> Remember, you'll only see a package in InBox if you push or round-trip, to see pull packages, look at the Zync Logs tab in GoZyncMobile for the last package processed: that will show you the fields on your hosted zync layout.
Changed lines 43-44 from:
-> The sync layouts in your file can not have script triggers on them.
to:
-> The sync layouts in your files can not have script triggers on them.
February 01, 2013, at 07:47 PM by 50.132.84.245 -
Changed lines 9-10 from:
-> You're trying to call some of the GoZync sub scripts without including our license file (unlikely).
to:
-> You're trying to call some of the GoZync sub scripts without including our license file (unlikely, unless you're trying to bypass the license).
February 01, 2013, at 07:46 PM by 50.132.84.245 -
Changed lines 7-8 from:
A pretty rare error, this can be caused by one of three things:
to:
Pretty rare, but if you're seeing this message it can be caused by one of three things:
February 01, 2013, at 07:46 PM by 50.132.84.245 -
Changed lines 7-14 from:
-> A pretty rare error, this can be caused by one of three things:

--> You're trying to call some of the GoZync sub scripts without including our license file (unlikely).

--> Some of your field, layout, or table occurrence names include prohibited characters (!~;&# etc) This is the most likely reason.

--> Or one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)
to:
A pretty rare error, this can be caused by one of three things:

-> You're trying to call some of the GoZync sub scripts without including our license file (unlikely).

-> Some of your field, layout, or table occurrence names include prohibited characters (!~;&# etc) This is the most likely reason.

-> Or one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)
February 01, 2013, at 07:45 PM by 50.132.84.245 -
Added lines 5-14:
!! License Violation Detected

-> A pretty rare error, this can be caused by one of three things:

--> You're trying to call some of the GoZync sub scripts without including our license file (unlikely).

--> Some of your field, layout, or table occurrence names include prohibited characters (!~;&# etc) This is the most likely reason.

--> Or one of your layouts is corrupt. For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error delete, that sync layout in your hosted and mobile file and recreate it. (These are the layouts in YOUR files, not on GoZynHosted, or GoZyncMobile.)

January 07, 2013, at 09:10 PM by 50.132.84.245 -
Added lines 13-14:
-> You'll also want to make sure that the mobile users are authenticated into your hosted solution (via GoZyncHosted) with a privilege set that lets them edit records. If all that sounds like stuff you've never heard of, this likely isn't your problem. This only comes up when folks have more elaborate security set ups.
December 29, 2012, at 09:58 PM by 50.132.84.245 -
Changed lines 23-31 from:
-> This is either because the related fields aren't on your sync layout, or that you haven't actually [[TriggeringRecordMods | triggered a modification in the parent record]].
to:
-> This is either because the related fields aren't on your sync layout, or that you haven't actually [[TriggeringRecordMods | triggered a modification in the parent record]].

-> It could also be that the portals on your sync layout use a relationship ''not'' based on the primary key of the layout's table. Portal data to be synced must be related to the primary key of the table the portal is on. More complex relationships should be synced as their own layouts.

'''Other things to check...'''

-> The sync layouts in your file can not have script triggers on them.

-> Visit the integration again in GoZyncHosted and click through the tabs for each table: tabs like "Field and Scripts" will run checks to make sure you don't have bad field names
.
November 11, 2012, at 11:43 PM by 50.132.84.245 -
Changed lines 9-10 from:
-> If the integration checks out with green check marks but you get NO sync action. Try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.
to:
-> If the integration checks out with green check marks but you get NO sync action, try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.
November 11, 2012, at 11:43 PM by 50.132.84.245 -
Changed lines 7-23 from:
-> More coming soon.
to:
'''Nothing works.'''

-> If the integration checks out with green check marks but you get NO sync action. Try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.

-> If that doesn't help it is likely your file references (Data Sources): more on checking those [[ExternalDataSources | here]].

'''Some fields not syncing.'''

-> The most common cause of unexpected sync behavior is that you're not syncing the layout you think you are. Remember, GoZync syncs the fields on your sync layout so visit the Integration in GoZyncHosted and make sure the layouts you've specified there are the ones you want to use.

-> Want to look closer? Turn of Field Level Merge in [[Zync Options]] and perform a sync for the table in question. Now visit the InBox in GoZyncHosted and export the last package: you'll see the fields being synced at the beginning of the package. If the fields you want to sync aren't there, they aren't on your sync layout in your mobile file.

-> Remember, you'll only see a package in InBox if you pus or round-trip, to see pull packages, look at the Zync Logs tab in GoZyncMobile for the last package processed: that will show you the fields on your hosted zync layout.

'''Related records not syncing.'''

-> This is either because the related fields aren't on your sync layout, or that you haven't actually [[TriggeringRecordMods | triggered a modification in the parent record]]
.
July 07, 2012, at 10:16 PM by 50.132.84.245 -
Added lines 1-4:
!! Processing the inbox

For errors processing the inbox in GoZyncHosted, see [[processing errors]].

Changed line 7 from:
-> Coming soon.
to:
-> More coming soon.
July 07, 2012, at 10:14 PM by 50.132.84.245 -
Changed lines 3-41 from:
-> GoZync uses SQL so you can't use reserved SQL words for any table occurrences or fields. You can't have a table occurrence named "time", for example.

!! How can I be sure my iPad / iPhone can see my FileMaker Server/ Host?

-> If you've gotten the External Data Sources between Mobile.fp7 and the hosted files ( GoZyncConnector.fp7 and GoZync.fp7) working in Pro, they'll work on your iOS device, provided your device can see your server/host. Not being able to see the host is usually only a problem for folks testing this on their local machines (people with IP addresses beginning 192.).

-> To test the visibility of your FileMaker Server / Host, you don't even need GoZync, you just need FileMaker Go on your iPhone or iPad:

--> Switch wifi off so the device is connecting to the internet over cellular.

--> Open FileMaker Go and get to the main "files" screen. In the right half of the screen, click the plus sign to add a host. Enter the IP address or name of your FileMaker Host and click "save". If you see files, or get asked for an account / password, your server is visible from outside the local network.

-> If you host isn't visible, check out the build in help for FileMaker Pro or FileMaker Server to learn about opening ports and exposing your server. You might also consider a third party hosting provider like %newwin% [[http://www.pointinspace.com | PointInSpace]].

!! Making sure updating new versions works?

Here is how you can be sure that the copy of your mobile file on your devices can [[DistributingMobileFiles | download new versions]] of itself.

-> '''1.''' Delete the copy of Mobile.fp7 on your iPad. Remember, renaming the mobile file is fine but: GoZync keeps a separate version number for each file name. So "Mobile.fp7" on your iPad can only download new versions of that file name: if you've renamed Mobile.fp7 to "MyFile.fp7" you need to first get a copy of "MyFile.fp7" on your iPad and the GoZync's new version routines will work with "MyFile.fp7". The rest of these instructions use "Mobile.fp7" but substitute your file name here if you've renamed it.

-> '''2.''' Quit FileMaker on the desktop and rename the Host folder as described above.

-> '''3.''' Open Mobile.fp7 locally in FileMaker Pro and visit the New File Prep layout to send a new version to the server: if you get errors you may need to double check the External Data Source references in Mobile.fp7.

-> '''4.''' Once you have a new copy up there, close Mobile.fp7 and email yourself a copy of Mobile.fp7: you'll open this email on your iPad and then it will be installed in FileMaker Go.

-> '''5.''' Now open Mobile.fpy back in FileMaker Pro (keeping the Host folder renamed to xHost) and  visit the New File Prep layout to send one more new version to the server: this will be one version higher than the one you emailed yourself.

-> '''6.''' At this point you can return to Mobile.fp7 on your iPad and click "Check for new version", downloading the build you uploaded in step 5 above. At this point you know that the file references in Mobile point to your served files. If you get an error here it is likely because your iPad can't see your FileMaker Server: it is behind a firewall or has a private IP address. Follow the instructions in FileMaker Server's built in help to open ports or otherwise expose your server / host to the outside world.

!! I can't upload a new version, it says "File Can Not be Created on This Disc"

-> It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use.

!! I'm getting more records than I should be.

-> If you're trying to zync 10 contacts (for example) and are getting many more than that, take a look at the resulting records in table view. If you see some of the correct contacts, but then a lot of records that only have the primary key (and none of the other values) it is likely that one or more of your SetField scripts is actually setting a field in the wrong table occurrence. In this contacts example, you get extra contacts by having any one SetField step from another table's Set Field script accidentally set a filed from a Table Occurrence based on Contacts.

-> If, on the other hand, you see lots of real contacts in there in addition to the ones you expected, then it is likely the found set in your source that is the problem: the found set just has the wrong records. See [[downloading found sets]] for more info.
to:
-> Coming soon.
June 25, 2012, at 03:35 AM by 50.132.84.245 -
Added lines 1-4:
!! General Gotchas

-> GoZync uses SQL so you can't use reserved SQL words for any table occurrences or fields. You can't have a table occurrence named "time", for example.

May 27, 2012, at 05:19 PM by 50.132.84.245 -
Changed lines 31-32 from:
It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use.
to:
-> It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use.
Changed lines 35-37 from:
If you're trying to zync 10 contacts (for example) and are getting many more than that, take a look at the resulting records in table view. If you see some of the correct contacts, but then a lot of records that only have the primary key (and none of the other values) it is likely that one or more of your SetField scripts is actually setting a field in the wrong table occurrence. In this contacts example, you get extra contacts by having any one SetField step from another table's Set Field script accidentally set a filed from a Table Occurrence based on Contacts.

If, on the other hand, you see lots of real contacts in there in addition to the ones you expected, then it is likely the found set in your source that is the problem: the found set just has the wrong records. See [[downloading found sets]] for more info.
to:
-> If you're trying to zync 10 contacts (for example) and are getting many more than that, take a look at the resulting records in table view. If you see some of the correct contacts, but then a lot of records that only have the primary key (and none of the other values) it is likely that one or more of your SetField scripts is actually setting a field in the wrong table occurrence. In this contacts example, you get extra contacts by having any one SetField step from another table's Set Field script accidentally set a filed from a Table Occurrence based on Contacts.

-> If, on the other hand, you see lots of real contacts in there in addition to the ones you expected, then it is likely the found set in your source that is the problem: the found set just has the wrong records. See [[downloading found sets]] for more info.
May 27, 2012, at 05:18 PM by 50.132.84.245 -
Changed lines 31-37 from:
It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use.
to:
It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use.

!! I'm getting more records than I should be.

If you're trying to zync 10 contacts (for example) and are getting many more than that, take a look at the resulting records in table view. If you see some of the correct contacts, but then a lot of records that only have the primary key (and none of the other values) it is likely that one or more of your SetField scripts is actually setting a field in the wrong table occurrence. In this contacts example, you get extra contacts by having any one SetField step from another table's Set Field script accidentally set a filed from a Table Occurrence based on Contacts.

If, on the other hand, you see lots of real contacts in there in addition to the ones you expected, then it is likely the found set in your source that is the problem: the found set just has the wrong records. See [[downloading found sets]] for more info
.
July 19, 2011, at 11:12 PM by 76.22.74.86 -
Changed lines 27-31 from:
-> '''6.''' At this point you can return to Mobile.fp7 on your iPad and click "Check for new version", downloading the build you uploaded in step 5 above. At this point you know that the file references in Mobile point to your served files. If you get an error here it is likely because your iPad can't see your FileMaker Server: it is behind a firewall or has a private IP address. Follow the instructions in FileMaker Server's built in help to open ports or otherwise expose your server / host to the outside world.
to:
-> '''6.''' At this point you can return to Mobile.fp7 on your iPad and click "Check for new version", downloading the build you uploaded in step 5 above. At this point you know that the file references in Mobile point to your served files. If you get an error here it is likely because your iPad can't see your FileMaker Server: it is behind a firewall or has a private IP address. Follow the instructions in FileMaker Server's built in help to open ports or otherwise expose your server / host to the outside world.

!! I can't upload a new version, it says "File Can Not be Created on This Disc"

It is likely that the privilege set you're logged in as does not have export rights: either log in as a full access user or extend the privileges of the account you'd like to use
.
July 04, 2011, at 06:27 PM by 76.22.74.86 -
Changed lines 1-2 from:
!! How can I make sure updating new versions works?
to:
!! How can I be sure my iPad / iPhone can see my FileMaker Server/ Host?

-> If you've gotten the External Data Sources between Mobile.fp7 and the hosted files ( GoZyncConnector.fp7 and GoZync.fp7) working in Pro, they'll work on your iOS device, provided your device can see your server/host. Not being able to see the host is usually only a problem for folks testing this on their local machines (people with IP addresses beginning 192.).

-> To test the visibility of your FileMaker Server / Host, you don't even need GoZync, you just need FileMaker Go on your iPhone or iPad:

--> Switch wifi off so the device is connecting to the internet over cellular.

--> Open FileMaker Go and get to the main "files" screen. In the right half of the screen, click the plus sign to add a host. Enter the IP address or name of your FileMaker Host and click "save". If you see files, or get asked for an account / password, your server is visible from outside the local network.

-> If you host isn't visible, check out the build in help for FileMaker Pro or FileMaker Server to learn about opening ports and exposing your server. You might also consider a third party hosting provider like %newwin% [[http://www.pointinspace.com | PointInSpace]].

!! Making
sure updating new versions works?
July 04, 2011, at 06:21 PM by 76.22.74.86 -
Added lines 1-15:
!! How can I make sure updating new versions works?

Here is how you can be sure that the copy of your mobile file on your devices can [[DistributingMobileFiles | download new versions]] of itself.

-> '''1.''' Delete the copy of Mobile.fp7 on your iPad. Remember, renaming the mobile file is fine but: GoZync keeps a separate version number for each file name. So "Mobile.fp7" on your iPad can only download new versions of that file name: if you've renamed Mobile.fp7 to "MyFile.fp7" you need to first get a copy of "MyFile.fp7" on your iPad and the GoZync's new version routines will work with "MyFile.fp7". The rest of these instructions use "Mobile.fp7" but substitute your file name here if you've renamed it.

-> '''2.''' Quit FileMaker on the desktop and rename the Host folder as described above.

-> '''3.''' Open Mobile.fp7 locally in FileMaker Pro and visit the New File Prep layout to send a new version to the server: if you get errors you may need to double check the External Data Source references in Mobile.fp7.

-> '''4.''' Once you have a new copy up there, close Mobile.fp7 and email yourself a copy of Mobile.fp7: you'll open this email on your iPad and then it will be installed in FileMaker Go.

-> '''5.''' Now open Mobile.fpy back in FileMaker Pro (keeping the Host folder renamed to xHost) and  visit the New File Prep layout to send one more new version to the server: this will be one version higher than the one you emailed yourself.

-> '''6.''' At this point you can return to Mobile.fp7 on your iPad and click "Check for new version", downloading the build you uploaded in step 5 above. At this point you know that the file references in Mobile point to your served files. If you get an error here it is likely because your iPad can't see your FileMaker Server: it is behind a firewall or has a private IP address. Follow the instructions in FileMaker Server's built in help to open ports or otherwise expose your server / host to the outside world.
(855) SEEDCODE
support@seedcode.com
Follow us: