AnsweredAssumed Answered

Updating a FileMaker Go solution and migrating data to new version

Question asked by fmdataweb on Aug 18, 2015
Latest reply on Aug 18, 2015 by CarstenLevin

I'm deploying a FileMaker Go solution that has a built in update mechanism - users can click a button to check for a newer version of the mobile database on the FileMaker Server and it will download the newer version if it exists. This is all working well, however I would like to expand this to include a way to migrate data from the current mobile database to the updated mobile database after it downloads (and replaces the previous one which has the same file name).


I would like to keep the list of files on the device clean so that it doesn't include lots of other files containing data that has been exported, so I'm looking at using the FM Go temp folder to export the data and then import that back in. I'm wondering if anyone has been down this road before and have some suggestions for how to handle migrating data without leaving a trail of files that appear in the list of files on the device?