sjopk.blogg.se

The DMT (as I've chosen to abbreviate it) attempts to solve the challenges associated with conventional migration strategies by bypassing the FileMaker application layer and copying data (and other supporting elements) directly from one file to the other, with table/field matching criteria that I'll describe further down in this article. Given a source file to pull data from, and an unopened clone file, the Data Migration Tool will create a new file based on the clone and copy data (and optionally accounts and value lists) from the source into the new file (by default called migrated.fmp12). And while this tool won't magically clean your corrupt data, it can help speed up the data repair process as described in the revert scenario. Revert: You have a corrupted file and need to revert back to a clean backup clone.īefore FileMaker 17, strategies for data migration typically included a scripted import process, which can be time consuming, not to mention comes with some limitations. The new Data Migration Tool (available to FileMaker Developer Subscription members) can help us tremendously with deployment scenario above.Deployment: A FileMaker app is deployed through multiple releases, and you need to pull the data from the previous app into the new version.To begin, let's first identify two common scenarios for when data migration is needed: Exciting to me anyway, because I geek out on technical stuff like this! One of the exciting new features released with FileMaker 17 is the Command Line Data Migration Tool. FileMaker 17: Data Migration Tool - Part OneĬolin Keefe, FileMaker Developer, IT Solutions