#Filemaker baseelements install
#Filemaker baseelements update
#Filemaker baseelements pro

Show Custom Dialog ĭetects the application architecture, then installs the appropriate version of a plug-in. This script step is not supported in server-side scripts performed by a FileMaker Cloud host.

#Filemaker baseelements 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.Because it captures everything in your solution, you can know more about your solution than its possible to know as a standard developer.

#Filemaker baseelements pro

Use the Get(ApplicationArchitecture) function to determine the current application's architecture. BaseElements is designed to be used by anyone who is using FileMaker Pro to develop systems either for themselves or for other clients. 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. Please download the latest MBS & BaseElements plugins and put them in the runtimes extensions folder. 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. Hello fellow FileMaker database developers. Built in use of the excellent fmSearchResults to allow you to search for specific text across your entire solution, and link directly to the results.

#Filemaker baseelements update

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. Your BaseElements files can be made available on FileMaker Server for sharing amongst multiple users with ease. Companies mostly use BaseElements to ensure their FileMaker solutions are more bug-free, absent of unused items, and serving up the cleanest code possible. Plug-ins must be enabled in the plug-in preferences for FileMaker Pro Advanced to recognize them. BaseElements is helpful for any FileMaker-based solution, especially for more complex solutions where finding things is like looking for a needle in a haystack. This function can help you determine whether the installed plug-in is newer or older than the plug-in required by the solution file. Im just getting my feet wet with the BaseElements (plugin, not analysis tool) and am a bit stumped. 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.