Baseelements insert install#
See FileMaker Pro Advanced Network Install Setup Guide. The system administrator can use the personalization file during an installation on multiple computers to disable plug-ins and prevent plug-in updates from installing in FileMaker Pro Advanced.Use the Get(ApplicationArchitecture) function to determine the current application's architecture. For example, the 64-bit version of FileMaker Pro Advanced can only install 64-bit plug-ins. FileMaker Pro Advanced can only install plug-ins that match the FileMaker Pro Advanced application's architecture.See FileMaker Server Help or FileMaker Cloud product documentation in the Product Documentation Center.
See Setting plug-in preferences.įor files hosted by FileMaker Server or FileMaker Cloud for AWS, the server administrator must enable the Install Plug-In File script step in Admin Console. If the Install Plug-In File script step installs a plug-in update but the plug-in is disabled in the plug-in preferences, FileMaker Pro Advanced installs the update but does not enable the plug-in. Plug-ins must be enabled in the plug-in preferences for FileMaker Pro Advanced to recognize them. This function can help you determine whether the installed plug-in is newer or older than the plug-in required by the solution file. You can use the Get(InstalledFMPlugins) function to identify the name, version, and enabled state of an installed plug-in. fmplugin.Ĭompressed plug-in files in ZIP format or plug-in files in TAR format can't be installed. In macOS, the plug-ins have the extension. If a non-plug-in file is located in the target or active container field, no action takes place when the script runs. Only FileMaker plug-in files can be installed. You must insert the plug-in in a container field before you can install or update the plug-in.
0 kommentar(er)
