All container fields are not syncable from MirrorSync 2 to 3

[Scotty Nordlund]

After upgrading to MirrorSync 3 from 2, I can no longer sync container fields.  During the reconfiguration process, I get the tooltip in the uploaded image below.  The tooltip says "Neither field is writable.  This could be because they are calculation or summary fields. It could also be caused by field-level validation or custom access privileges.".  These container fields are not calc or summary fields.  There is no field level validation or custom access privileges that I know if.  They are full access, and the fields have not changed since my last MirrorSync 2 configuration.  Please help!

Edited October 10, 2016 by Scotty Nordlund

[Jesse Barnum]

Is the hub database MySQL?

Try this build to see if it solves the problem:

http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 3.1001.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1478736563&Signature=HF42GUAbFqmk5UkMdY99%2FSK8p7M%3D

[Scotty Nordlund]

The hub database is FileMaker. I'll try this build in the morning. Thanks!

[Jesse Barnum]

Scotty, I was just able to reproduce the problem you were having. The build I sent you won't fix it, I'll send an updated one tonight or in the morning.

[Jesse Barnum]

Just sent the update via our issue tracking system. Also posting here in case anybody else has the same issue:

http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 3.1002.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1478757191&Signature=cpEQlKMYZeqOzBH%2B4YwlPsha%2FVw%3D

[Scotty Nordlund]

Back in business Jesse!  Thanks so much, you guys rock!

Edited October 11, 2016 by Scotty Nordlund