![]() ![]() If a function can return an error code other than a 1552, it will be documented with the description of the function below. However, some plugin functions will return different error codes. Generally, if there is an error, our plugins will return an error code of 1552 when Get(LastError) is called. Please see the FileMaker documentation for how to handle errors appropriately. When calling plugin functions as script steps, you will handle errors in the same manner you would any other FileMaker script step. Any other script call made from FileMaker Pro in any solution, hosted or not, will execute on the local machine and will require the plugin to be installed there. This is not the case unless your script is being called using the Perform Script on Server script step. It is also a common mistake that when installing the plugin on FMS, that any script call made from a hosted solution will be executed with the plugin installed on FMS. It can be removed once the scripts have been written. In order to write scripts that will be executed server side, you will need to install the plugin for FileMaker Pro. Note: It is a common mistake that installing a plugin in FileMaker Server will give you access to the plugin's functions in the FileMaker Pro script workspace in a hosted solution. You can also set a field or a variable to the return value of the function by checking the "Results" checkbox (see screen shot below) Give the parameter the appropriate value and click ok. This will open a drop down menu where you can specify the value of the parameters as well as a few other options ( see image below).Ĭlick "Specify" next to the parameters to give them a value. ![]() To further define the parameters of the script step, click the options button next to the script step. Either option is completely viable but it will be up to you to decide when either option is appropriate. You can also call plugin functions by setting the plugin function as the value of the variable. In FileMaker 16, plugin functions will be listed here ( highlighted in red in the image below). Available script steps are listed on the right of the script workspace. You can also just start typing the name of the script step or use its type-ahead designation. To add a script step to the a script, double click it and it will add the step to your script. To edit an existing script, click on it in the list of scripts on the left and then start editing it. To create a script, click the "+" in the upper left corner. This opens the script manager, where you can create new scripts or edit existing ones. To create a script, open the script manager from the menu bar of your FileMaker database. As plug-ins are used within FileMaker, you can use scripts to control the actions of plugins. Script steps are generally composed of a Function, which defines the action that the script performs, and Variables, which define the parameters of the action. They can be simple or complex, made of variable script steps. Scripts are commands that cause FileMaker to perform specific tasks. However, using the tools that Plastic provides and using FileMaker’s existing functions will allow you to build your system from the ground up.Ĭreating Scripts, Calling Functions, and Setting Variables For example, purchasing 360Works’ Plastic plug-in will not give you an out of the box point of sale system. Think of plug-ins as the tools you need to build a specific solution within FileMaker. Please refer to our Plug-In Licensing page. ![]() ![]() (For further reference, check FileMaker's official plug-in installation docs) Getting Started with Plug-Ins Plug-in Installation By utilizing FileMaker's standard functions to perform non-standard tasks, plug-ins help ensure that your information is accessible, organized, and integrated. Without plug-ins, users would need to purchase additional stand-alone software that may not interface with existing FileMaker databases. By allowing developers to expand the functionality of FileMaker without changing its core structure, plug-ins ensure that FileMaker maintains its broad user group while meeting very specific needs. A plug-in's functionality can range from improving FileMaker's ability to send emails to allowing FileMaker to run custom Groovy code at will. Plug-ins do not stand alone, and are instead only used to extend FileMaker's capabilities. 2.4 Creating Scripts, Calling Functions, and Setting VariablesĪ plug-in is a file that can be installed to add new functionality to FileMaker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |