« Last early bird ticke… | Home | Disable tab panel ite… »

Tips for FileMaker Data Migration Tool

You may have seen the release of the FileMaker data migration Tool. And you can read documentation here. We got a few extra tips for you here:



First, be aware that matching of tables is by name or ID. So please do not reuse field or tables names. Because due to name matching, if you drop a table with a given name, a few days later add it again for a different reason, the migration could move data from the old table to the new table and match fields just by ID. This can cause serious problems, if data ends up in a different column or table!

e.g. if you have a table test with ID, FirstName, LastName, Job. Than later in development test is deleted. Days after that you create a new table named test with fields Product ID, PersonID, Payment, ID which is totally unrelated to the old table. But now when you migrate, the data from FirstName ends up in PersonID, if those have a matching internal field ID!

Second, please don't use the normal full access account to migrate. Better make a new account with a privilege set where everything is forbidden except the privilege named fmmigration. This privilege name can have an unique add-on, e.g. fmmigrationMySecret and that must match between source and clone files to allow migration. And you want to use that to avoid anyone with an account to just migrate your solution to steal the data.

Third, please be aware that using the normal Terminal window involves using a shell application, which may (or may not) store a permanent history of commands. See man page of history command to clear. This may include passwords. Also the command line may be visible with other tools while running like ps tool. So never ever put your full access password there as the trouble with someone seeing it, is big.

Forth, please check the MBS Shell functions to run the FileMaker Data Migration Tool. MBS plugin can run several shells in parallel to migrate several files parallel and better use CPUs to get the jobs done quicker. Our plugin can return you the messages output by the tool and if you run it directly, no bash is involved, so no history is written. By using our write commands, you can even send text like passwords in memory to the tool. Passing parameters does not need quoting with out shell functions, as you pass each parameter as a parameter to the plugin function.

Here is a sample script:

Set Variable [ $shell ; Value: MBS( "Shell.New" ) ] 

Set Field [ Shell::Output ; "" ] 

Set Field [ Shell::Error ; "" ] 

Commit Records/Requests [ With dialog: Off ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "-src_path") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "/Users/cs/Desktop/Contacts.fmp12") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "-clone_path") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "/Users/cs/Desktop/Contacts Clone.fmp12") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "-target_path") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "/Users/cs/Desktop/Contacts target.fmp12") ] 

Set Variable [ $s ; Value: MBS( "Shell.AddArgument"; $shell; "-v") ] 

Set Variable [ $s ; Value: MBS( "Shell.Execute"; $shell; "/Users/cs/Downloads/FMDataMigration") ] 

Set Variable [ $error ; Value: "" ] 

Set Variable [ $result ; Value: "" ] 

If [ MBS("IsError") ] 

    Show Custom Dialog [ "Failed to run" ; $s ] 

Else

    If [ Length(Shell::Input) > 0 ] 

        Set Variable [ $s ; Value: MBS( "Shell.WriteInputText"; $shell; Shell::Input; "UTF-8") ] 

    End If

    # Loop while app runs and collect messages

    Loop

        Set Variable [ $s ; Value: MBS( "Shell.Wait"; $shell; 1) ] 

        Set Variable [ $error ; Value: $error & MBS( "Shell.ReadErrorText"; $shell; "UTF-8") ] 

        Set Variable [ $result ; Value: $result & MBS( "Shell.ReadOutputText"; $shell; "UTF-8") ] 

        Set Field [ Shell::Error ; MBS( "Text.ReplaceNewline"; $error; 1) ] 

        Set Field [ Shell::Output ; MBS( "Text.ReplaceNewline"; $result; 1) ] 

        Exit Loop If [ MBS( "Shell.IsRunning"; $shell) ≠ 1 ] 

    End Loop

    Commit Records/Requests [ With dialog: Off ] 

End If

Set Variable [ $r ; Value: MBS("Shell.Release"; $shell) ] 



Finally, if you build something, be aware that you may not have the right to redistribute the FileMaker Data Migration Tool on your own. FileMaker developers need to have a FDS subscription to be allowed to download it.
09 06 18 - 10:51