It is slowly dawning on me how much we reply on the FMDataMigration tool nowadays, which has now joined 2empowerFM Developer Assistant and Perception as our ‘can’t do without’ utilities.
Although we use both the Mac and Windows versions, it is used on Windows most frequently, and even though most of our solutions are separated, it has significantly improved productivity.
Mostly we keep the syntax needed as text within secure storage (stored locally, not on any server) with predefined paths to our working folder.
Our standard procedure is:
Create the clones on our development server using a dedicated backup in FMS Admin Console
Transfer to the live server and store in a ‘Clones’ folder then remove the ‘clone’ suffix(es)
Stop FMS and copy the live files to a ‘Data’ or ‘Originals’ folder
Run the command line as administrator and navigate to the FMDataMigration folder within this
Copy and paste the syntax for each file, which creates the new files in a ‘New’ folder (there are tools out there to remove the need to learn or setup the syntax)
Copy the new files to the FMS data folder (no permissions issues in Windows, or set permissions if a Mac)
Archive the original files
Delete the clones
The tool reduces the need to attempt to keep the field creation in sync between the live and dev versions and can allow full updates to be completed in minutes. For the introduction of a new system, we may be doing a number of these each week.
Thank you Claris for this wonderful utility and, if any developer out there hasn’t used it, I strongly suggest you try it. This has massively increased the value of a FileMaker Developer Subscription.