Data sources best practices

Below are some best practices to follow when working with FileMaker data sources in Claris Studio

FileMaker Pro is the source of truth

Always remember that FileMaker Pro is the "source of truth" when working with data sources in Claris Studio. While rare, in the event that there's a conflict between records in Claris Studio and FileMaker—for example if the host gets disconnected (see FileMaker Server restarts or disconnects below) and records are edited in Claris Studio—the corresponding records in FileMaker will take precedence and will override the recent changes made in Claris Studio.

FileMaker Server restarts or disconnects

If a FileMaker Server host used to connect a data source needs to be restarted or is disconnected temporarily, there is a potential for recent changes to be lost if records are edited in Claris Studio and FileMaker while the host is offline. Because FileMaker takes precedence over Claris Studio, records edited in Claris Studio while the host is offline will be overwritten by FileMaker when the host comes back on line and records are synced again.

We recommend:

• Planning FileMaker Server restarts during off hours to minimize the chance of records being edited in Claris Studio while the host is down.

• Exporting any changes made in Claris Studio while the host was down so that it doesn't accidentally get overwritten by FileMaker when the host comes back online.

• Syncing from FileMaker once the host is back online to refresh the connection.

In most cases, new records created in Claris Studio during this time should not result in a conflict and will be synced properly.