Normally, you would need to download all PDF files to the client via container fields, export them somewhere where they can be manipulated and then combined and finally re-uploaded the result to another container field. It also does not matter if you have external storage enabled for container fields, since FileMaker takes care of that part for you.Īnother benefit is the savings in networks latency if this action were to be performed on the client. Encode/decode Base64 to create text files on the flyīy performing this script on the server, there is no need for third party plugins to be installed on the client, which also makes it compatible across the platform and supports FileMaker Go and WebDirect.Integrating with a 3rd party server-side program.Performing command line scripts on a server.Some of the techniques used in this example: May not appear in function lists.I believe this is a good example, in part because it combines several techniques, each of which has value. Internal : a very specific and custom function designed for use in BaseElements and likely not very applicable to the general public.Beta : new functionality with an as yet indeterminate feature set, so may change, or may even be removed.These functions have native alternatives in the current BE release and will no longer appear in the function list, but do still work if used. However, others although they are replaced completely, might still have a use : eg the ValuesSort function in BE has shown to be faster in some situations than the internal one.ĭeprecated : has been made redundant or otherwise no longer supported, and will be removed in a future version, likely in the next major release. Some functions like the HTTP functions can be removed soon and probably will as they are completely superseded by the new HTTP functionality in FMP 16. Obsolete : has been made redundant by native FMP functionality, but we haven't yet removed it from the plugin. No value - untested or functionality is indeterminate.Īctive : still in development and supported.BE versions 4.2.0 are also compiled for native compatibility on Apple Silicon. BE Plugins prior to 4.2.0 run just fine under Apple Silicon such as the M1 under rosetta ( in FileMaker Pro for intel processors ).All releases from 4.0.5 and later are signed, and older versions can be signed on request. FileMaker version 18 and later require signed ( and notarised on Mac ) versions of the plugin to install without warnings.Versions prior to 4.0.4 are NOT thread safe and caution should be taken to only use a single instance of the plugin on FMS at one time. As of version 4.0.4 the plugin is now thread safe, and will run on FileMaker Server where there are multiple instances of scripts being called at the same time.BE plugin versions 4.0.4 and later require Mac OS 10.13 or later.The BE plugin does not run in Windows XP as of BE version 3.1 and later.Downloads of 32bit BE 3.x are available on the download page. So you can't run BE 4.x in FileMaker Pro 32bit for Windows or older versions of Mac that are 32 bit. Plugins in general, ( including BE ) DO NOT run in these platforms as they don't have plugin support as an option : Compiled FileMaker apps for iOS built with the iOS SDK, and under Xcode in the simulator on MacOS.FileMaker Server for Mac ( Intel or Apple Silicon ), Windows, Linux ( x86 only ).FileMaker Pro on Mac ( Intel or Apple Silicon ) and Windows.Short version : BaseElements plugin runs in Some functions won't work on some platforms and some functions will still run but give you false results - we don't trap for platform within the plugin itself, so it's up to the developer to call appropriate functionality for the platform they're developing for. This document assumes the latest version, and will sometimes also include beta versions. Operating System and FileMaker compatibilty
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |