Hello, Jesse:

The first show-stopping issue I came across today was that I never got the screen for foreign key mapping, and when I got done, it did not draw any lines between the 17 tables I chose for synchronization.

First screen after selecting the database to be used from the server:

Next screen after selecting the Primary Key and Modification TimeStamp Mapping (skips foreign key mapping totally):

I deleted the previous config, as well as the user that I attempted to setup (in Licensing), quit the utility, then refreshed my browser, downloaded the utility again, clicked "New" (after deleting that user from Licensing again), went through the steps of choosing Primary keys and modificationTimestamps, and it still skips the Foreign key mapping. When I chose "Cancel" at the final screen that says "Database Setup", this is what occurs:

Looking forward to your ideas on how to "fix" this so we can try again to test for deployment.

- - Scott

That is because you're using UUIDs, and UUIDs stay the same on all devices. We only need to configure foreign key mappings when using sequential numbers for primary keys, because those change when they are synced to different devices, and we need to know which foreign key values to update.