Save a Copy as Add-on Package
Creates an add-on package from a FileMaker Pro file.
See also
Options
-
Window name specifies the window name of the open FileMaker Pro file to save. If not specified, the file for the current window is saved.
-
Replace UUIDs generates new UUIDs for all elements in the file before saving as an add-on package. This action can't be undone.
Compatibility
Product | Supported |
FileMaker Pro | Yes |
FileMaker Go | No |
FileMaker WebDirect | No |
FileMaker Server | No |
FileMaker Cloud | No |
FileMaker Data API | No |
Custom Web Publishing | No |
Originated in version
19.0
Description
This script step creates an add-on package from an open FileMaker Pro file. The add-on is saved in this folder:
-
Windows:
<drive>:\Users\<user>\AppData\Local\FileMaker\Extensions\AddonModules
-
macOS:
/Users/<user>/Library/Application Support/FileMaker/Extensions/AddonModules
In this folder, the add-on is saved in two forms:
-
An uncompressed folder containing the files that make up the add-on. The current FileMaker Pro installation loads the add-on from this folder and makes it available immediately to install the add-on in your custom apps.
-
A compressed .fmaddon file that you can distribute to other users. Users with FileMaker Pro installed can double-click the .fmaddon file to add the uncompressed add-on folder to the above location on their computer.
For more on how to create an add-on, see the Knowledge Base.
Notes
-
If the script to create your add-on package is in the same file that you want to save as an add-on package, add the following to the beginning of your script's name to prevent it from being included in your add-on:
__FMAddonTemplateDirectives_
Note that this prefix begins with two underscore characters (__) and ends with one underscore.
Example 1
Saves as an add-on package the file whose window name is My Add-on.
Save a Copy as Add-on Package [ Window name: "My Add-on" ; Replace UUIDs: Off ]