Here's the error message:

Missing field ...; it has etiher been re-named or dleted in the local file.  ....

 

I am running the current version of MirrorSync (downloaded yesterday)

Filemaker Server 13 running on Amazon Web Services

Filemaker 12 and Filemaker Go as the spokes

 

I ran the setup process, created a link to download the full file (not a close).  Used the link to download to my Ipad.  The link worked, file was downloaded, file appears to function in FM Go, but sync fails with the above error.  Same result on my mac. 

 

I am running this from an admin account, so I don't think its related to the privilege sets.

 

Thoughts?

... and what made you think renaming or deleting a field would not give an error?

Why would I post a question if I had deleted the field?

The field is in the database. Both on the server and on the version I downloaded using the link created by mirrorsync.

Here's more info:

 

## set global fields for sync process section:

$$disableSchemaValidation set to FALSE

 

## Begin gathering total record count into $$json variable

 

If (not  $$disableSchemaValidation)

Then $$MIRRORSYNC_ERROR is set to indicate fields are missing or changed.

 

Once $$MIRRORSYNC_ERROR is not empty, this sets up the sync script terminate and indicate failure of the sync

 

This really is not making any sense to me.

Also, I've re-run the setup process confirming the settings and build. Same result.

pcl549, does your database name contain periods (.)? If so, there is a bug in FileMaker's design functions that prevents this from working. We've got a workaround for this in our development build of MirrorSync.

 

If that's not the issue, then would it be possible to send me a copy of your database, along with a developer account that I can use to look at the MirrorSync script? If so, please upload it to http://360works.com/upload

Awesome! Thank you so much. It does contain a period. I'll fix and rerun and let you know the result. Thanks!

I renamed the file to remove the period, reran the set up and it worked. Problem solved. Thank you very much!

Good to hear!

 

FWIW, the next release of MirrorSync works around this problem, so it won't be a problem to put periods in filenames.