How to Troubleshoot Writeback Failures

[millennium]

We have a FileMaker database with corresponding fields in MariaDB. When records are created in SQL, they are sync'd with FileMaker and the record is indeed created and the writeback field has an auto-incremented value, but the writeback field is not always "written back" to SQL. What is worse, if the record is modified in SQL, the null value in the writeback field is sync'd back to FileMaker so that a field which is defined as Indexed, Auto-enter Serial, Always Validate, Unique actually winds up with a null value!

Any idea how to troubleshoot this problem. We can recreate it quite frequently.

[Jesse Barnum]

Please try this version (6.1261). I've added some improvements to the write-back function. Just double-click the installer on the server to update the version, and try the sync again.

https://s3.amazonaws.com/com.prosc.store.downloads/MirrorSync/360Works+MirrorSync+6.1261.zip

--Jesse Barnum