Here is an overview of all our plug-ins that have been tested to work with FileMaker 19 (and also FileMaker Pro 18, 17, 16 and 15). Overview of Troi Plug-ins for FileMaker 19 So there is no need to change your function calls when converting to FileMaker 19. The plug-in architecture has not changed in FileMaker 19. Please see below for an overview of all Troi plug-ins and their compatibility with FileMaker 19. claris filemaker 19 overview db services June 4th, 2020 - claris filemaker pro 19 filemaker pro is no longer called filemaker pro advanced and this marks the last annual release of claris filemaker pro claris will adopt an agile development methodology that includes more rapid release schedules eventually we expect claris will name the product. For more information on how our code signatures look, see the correct code signatures of Troi Plug-ins information. I would expect it will not work as you wish, as OnObjectKeystroke will fire for each character in the string. Try the script without the IF clause to see if you script trigger fires properly. When you install a plug-in that is not code-signed, FileMaker 19 will give you a warning.Īll current Troi plug-ins are code-signed. 1 Answer Sorted by: 0 The Code (Get (TriggerKeystroke)) returns the ASCII code for a SINGLE keyed-in character and will never match your string. A valid code signature assures the user that a plug-in is valid, unchanged and made by a certain developer. ) Summary Running plug-ins with FileMaker 19įileMaker 19 (as does FileMaker 18) will still check if plug-ins are code-signed.

(This page was first published on and last updated on May 5, 2021. The web page with information regarding compatibility of our plug-ins with FileMaker 18 is still available here. We will update this page when we release new versions of our plug-ins.

Here you’ll find some information regarding compatibility of Troi Plug-ins with FileMaker 19.

Filemaker advanced 19