Write-backs for MySQL and Filemaker syncing

July 15, 20169 yr

This is about a Filemaker Server <--> MySQL sync setup.

I have two fields, serialNumber and writeBackNumber, and an altogether separate primaryKey that isn't used for this part.

If I create a new record on Filemaker, everything is fine. the serialNumber is auto-incremented on record creation and synced successfully.

However, If I create a new record in MySQL, I can leave both serialNumber and writeBackNumber blank, but when the sync happens, Filemaker does not auto-increment the serial number and put it in the field. It looks like it's just skipping the auto-enter part altogether and leaving serialNumber blank. This seems like what's going on:

Create new record in MySQL. serialNumber and writeBackNumber are blank.
Click sync, 1 record gets synced to Filemaker.
Record appears in Filemaker with both fields blank.
Click sync, that record gets erased from MySQL but is still in Filemaker.

Is this a bug?

Do I need to edit the MirrorSync customization script to perform the auto-enter on hub (Filemaker) pre-sync and then copy that over to the spoke (MySQL) post-sync?

July 16, 20169 yr

In your configuration, which is the hub and which is the spoke?

July 18, 20169 yr

Author

Filemaker Server is the hub and MySQL is the spoke.

July 20, 20169 yr

Author

Please let me know if this is a question I should direct to email support instead?

July 25, 20169 yr

Hi Roger - I'm sorry for the delay, I just got back from DevCon and am catching up now.

I will work on reproducing and fixing this problem. Is it OK for you to use MirrorSync 3? I'm not planning on fixes to version 2.x anymore.

July 26, 20169 yr

Author

Yes, of course! Downloading v3 now. The prototype is almost finished and we are ready to buy a full license for MirrorSync 3 if we can get resolve this problem. Thank you for the help!