![]() ![]() ![]() You can use a script that runs via the On First Window Open trigger, to check for the latest version and install it if required. The scripted install is the best way to keep plugins up to date on any system that is being used constantly and where you want to check that the plugin is active before you let a user do tasks that require the plugin. Recommended : Scripted Installation for Client or Server There's also different locations on server for different functionality, so a plugin that does a calculation that displays in WebDirect will need to be installed for that, and will be a different location than one for Perform Script on Server scripts.Īlso when you use plugin functions inside stored calculation fields, these can often be evaluated on the server, so the plugin needs to be installed there too. And some behaviours, especially around file paths, will be different on each platform. Each FileMakerPro client will need to have a copy of the plugin installed locally for them to be able to use plugin functions inside scripts and calculations that run on the client.Įach FileMaker Pro client with a different OS needs a different plugin - so there are different files for Mac vs Windows for example. You can install plugin on FileMaker server - this doesn't not do anything for FileMaker clients being able to use plugin functions though. The first thing to understand is the difference between a server and client install. fmplugin file, now what do you do? Server vs Client installs ![]() You've downloaded the plugin file, and got a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |