MirrorSync makes it extremely easy to setup a default configuration, while still giving developers the flexibility to customize the process.
MirrorSync lets you select which tables, records, and fields to sync, as well as the sync direction for each table. Run scripted actions before, during, and after your sync operations, such as sending an e-mail when a job is completed. You can use traditional FileMaker scripting to limit the records which will sync.
It will allow you to either sync a copy of the database from your FileMaker Server, or sync with a separate task-specific mobile database. If you are syncing with a separate mobile file, the setup process lets you simply drag and drop fields and table names to match them up, like a typical FileMaker import.
You can also easily control sync direction: One-way from server to mobile file, one-way from mobile file to server, or bidirectional. This can even be set separately for each table.
Here are a few of the options that you can configure in the MirrorSync setup process and customization script:
- - If the same record is modified on different devices, you control whether or not MirrorSync automatically merges the changes, prompts the user, emails an administrator, or picks the most recent change.
- - You control all of the dialogs and messages that are displayed to the user, and whether or not to display them at all.
- - You can either let the user sync with their same server username, or specify a sync account for them.
- - You can write FileMaker scripts to run before records are deleted, and after they are inserted or updated.