#FILEMAKER PRO UPGRADE PATCH#
Optionally, you can then encrypt the patch file (see Securing an upgrade).
#FILEMAKER PRO UPGRADE UPGRADE#
After you create the patch file, use the upgrade tool to validate the file and fix problems until it's valid.Compare the v1 and v2 FMSaveAsXML files and use that information to create a patch file. Then in FileMaker Pro, choose Tools menu > Save a Copy as XML or use the Save a Copy as XML script step to create an FMSaveAsXML file of both versions of your app. After you develop version 2 (v2) of your app, use the upgrade tool to generate GUIDs in v2 of your app.This operation adds GUIDs to any objects that don't have them. Because a patch file that deletes or modifies existing objects must reference those objects with globally unique identifiers (GUIDs), you must run the upgrade tool with the ‑‑generateGUIDs subcommand on the original version (v1) of your app before you distribute it to customers.The upgrade tool does not support migrating, adding, modifying, or deleting record data, including externally stored container data.For example, *Action element refers to an AddAction, DeleteAction, or ReplaceAction element. *Name element: Any XML element name with the Name suffix.catalog: A collection of objects in an FMSaveAsXML file or patch file.object: An element in an FMSaveAsXML file or patch file that describes an individual item in a FileMaker Pro file-for example, a field, table, script, script step, layout, or layout object.You use this file to help create a patch file. This file is an XML representation of the FMP12 file it was saved from. FMSaveAsXML file: An XML file created via the Save a Copy as XML command or script step in FileMaker Pro.A patch file may be plaintext or encrypted. patch file: An XML file that specifies the actions (add, delete, and replace) to perform on the source file.destination file: A copy of the source file that has been upgraded using a patch file.source file: An FMP12 file to be upgraded.
#FILEMAKER PRO UPGRADE FULL#
For full releases of an app or to add or modify objects and properties not supported by the upgrade tool, use the FileMaker data migration tool instead. This approach keeps the patch file relatively simple and primarily for adding objects to an app. The best practice for using the upgrade tool is to provide quick, short-term fixes to problems between full releases of an app. A developer wants to remove sensitive debug data or functionality that was not intended for distribution to customers.A developer wants to provide a critical bug fix to all customers.A developer requests a customer to apply a temporary debug patch to an app to track down or mitigate an issue the customer is having.A customer wants to upgrade to a newer version of your app but doesn't want to lose, or can't migrate, their data and their schema or layout customizations from their file to a new file.Note:This tool is provided as a developer preview.Ĭommon use cases for the upgrade tool are: