Hi!

Check this log out:

Code: Select all

---------------------------------------------------------
00:00:00 - 00:01:05 - STARTING PROJECT PULL


00:00:00 - 00:01:05 - Starting Pull
00:00:00 - 00:01:05 - Starting to Pull "gzh_PROJECT"
00:00:00 - 00:01:05 - Last Time Zync: "21/11/2013 14:30:10"
00:00:00 - 00:01:05 - FLM is OFF
00:00:00 - 00:01:05 - Starting TO Filter - "gzh_PROJECT"
00:00:01 - 00:01:06 - Found 295 Records in the filter
00:00:00 - 00:01:06 - Looking for record to Delete
00:00:00 - 00:01:06 - no records to delete in "gzm_PROJECT"
00:00:00 - 00:01:06 - Deletion Complete
00:00:00 - 00:01:06 - Constraining filter records by last time zync
00:00:00 - 00:01:06 - Found 3 records that have changed since last zync
00:00:00 - 00:01:06 - Starting sync on 3 records.
00:00:01 - 00:01:07 - Sync complete!
00:00:00 - 00:01:07 - Done Pulling "gzh_PROJECT"

00:00:00 - 00:01:07 - Pull Complete

00:00:00 - 00:01:07 - ENDING PROJECT PULL
---------------------------------------------------------


So, on the production system, we've got 295 Projects showing up. I do the sync on the iPad, GoZync finds 295 (all) Projects and syncs them.

I open the newly synced version on the iPad, and guess what, yes, that's right, only 291 projects are there.

I have found a two week old Project record which will not sync. I have not been able to see why that record will not show up on the iPad, or what makes it different. I have edited it, I have changed the LastTimeZync field to refresh it, I have refreshed GoZyncMobile and still nothing.

Any one have a clue? What happens when GoZync tries to edit a locked record? Newly created records are downloading fine, editing older records works fine too, what to do?

Any help or clues would be greatly appreciated.

Thank you!
Pablo

This is probably either an issue with some specific data in one of those records, or a field validation you have set up that one of those records is failing. Make sure there are no strange characters, including trailing carriage returns, in the primary key field for those records. And either make sure those records satisfy any field validations you have set up, or just temporarily turn them all off to see if that's the cause. HTH... Jeff

Hi Jeff,

Thanks for the quick reply.

I thought that validation errors would result in GoZync informing me of an error. Anywho, the validation seems fine on the Project, but would it fail if perhaps a related record of the Project fails? (i.e the related Client, or Contacts, etc.)

Thanks,
Pablo

If you've set up related synching then yes, if GoZync is unable to create or edit a record because of a field validation failure, that will cause a problem regardless of whether it's a parent record or a child record that fails the validation. I would suggest making a duplicate copy of your entire folder, then strip out all field validations in all tables in your hosted and mobile files and try synching. If it works, then you can start looking for the exact cause of the validation failure. My guess is there's something about record #292 that isn't satisfying one of your field validations. If you still can't figure it out, send your files to me at [email protected] and I'll have a look.

Thanks for the feedback Jeff.

However, I created a script to loop through all the records, open the record, modify the gz_ModifyTime to set the current timestamp, commit the record and move on to the next one.

I have run this script on all general tables, nothing comes up. Could I perhaps insert a step onto the GTTR script to pause on a validation error? Seems weird that there is no reported errors anyways as the sync reports that everything went well.

The other thing that has me scratching my head is the fact that if a record failed standard filemaker validation, why did it commit? The records that are not syncing are input by the users.

Im running out of ideas

I don't understand what you're trying to do with that script you say you created. If you're still having problems you can't figure out, send your files to me at [email protected] and I'll have a look. Please be sure to include the full-access login information as well as a detailed description of the problem and instructions for how I can reproduce it.