Updating plug-ins
You can use calculations and scripts to check the version of installed plug-ins, then update plug-ins with plug-ins stored in container fields in a FileMaker Pro file. To see examples of script and calculation syntax, see Plug-in update example.
To update plug-ins:
1.
In the solution file, create a table to store plug-in information.
2.
In the table, define:
 •
a text field for the plug-in name
 •
a text field to store the description of the plug-in
 •
a number field for the plug-in version currently required by the database
 •
unstored calculation fields for the version and enabled state of the plug-in that is installed in the FileMaker Pro file.
 •
a container field to store the plug-in file
3.
Create a layout in which to display the stored plug-in and, optionally, descriptive information about the plug-in, then add to the layout the appropriate fields you created in step 2.
Note  While you need only the container field on the layout, you might consider adding the plug-in name, description, and version number fields so you have access to this information.
4.
Create a script that compares the version of the installed plug-in with the version of the required plug-in, then uses the Install Plug-In script step to update the plug-in, if needed.
5.
Create a script that alerts users to possible plug-in installation error conditions, if the plug-in cannot install.
6.
Create a script that checks to ensure the installed plug-in is enabled.
7.
Create a start-up script that references the above scripts, in their script order, when a user opens the database.
Notes
 •
Clients must be running FileMaker Pro 12 or later to update plug-ins using this method.
 •
For plug-ins to install, the Allow Solutions to Install Files option must be selected in the client’s Plug-in preferences. See Setting plug-in preferences.
 •
If a plug-in has been disabled in the client’s Plug-in preferences, it will install but will not be accessible until it is manually enabled by the user.
 •
Only one plug-in can be stored in each container field, but you can view all plug-in information by creating multiple plug-in container fields on a single layout.
Related topics 
Creating custom plug-ins
Installing plug-ins
Get(InstalledFMPlugins)
Install Plug-In File
Was this topic helpful? Send feedback.