AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Baseelements plugin filemaker12/6/2023 ![]() ![]() It uses the Save As XML formats to document the changes, and can be automated in a closed FileMaker file.Īlthough the tool itself is documented well, the process to build a “patch” file is only described. This is going to be the start of a huge shift in how we do changes to solutions in FileMaker. However alongside FileMaker 19, we also got the release of the “ Claris FileMaker Custom App Upgrade Tool” which is complementary to the data migration tool we’ve previously seen. FileMaker now has a “Save As XML” option which is great for for documenting a solution, but still not quite a DDR replacement. I think the other interesting aspect of FileMaker 19 is how the platform is talking about developer tools and how we integrate directly with our solutions out in the field. A insightful take on this is from Todd Geist, describing FileMaker 19 as the “ first open platform“. This release is a big one in terms of the changes and direction in the platform, and the deeper integration of JavaScript and the Data API into FileMaker Pro client is going to be massive. However generic accounts can still benefit from its results when that CF's used in calculations provided by the solution developer!Īs any user can benefit from such a CF –which can be used by the developer here and there- there is not need to assign this privilege to any script that is using it!įull Access Privileges option aims at letting a common user do things beyond his privileges and avoiding him (if developer's wrongly set his Script privilege to Modify All ) to have access at that script.As always we are hot on the heels of the FileMaker Pro 19 release to announce a new version of BaseElements, v 19.0b1. When you set the CF Avalaibility to "Only accounts assigned to full access privileges", you are instructing FileMaker to give no access to that CF to accounts with lower privileges.Īs generic accounts already can't edit any custom function, its purpose is avoiding them to use the CF in their own calculations. I've found a couple of conceptual errors in your digression about CF (the secret token!) and Scripts so let me clarify a couple of things about security: If you have the need for integrating true REST client functionality within a FileMaker solution, then you’ll be glad you watched this video! ![]() It uses the very popular cURL library behind the scenes and with a little bit of knowledge, you’ll be interacting with web services in no time. The plugin can access pretty much access any web service and will allow you to perform the full suite of possible interactions. One of those options is the freely available BaseElements plugin. If you’re ever going to work with a truly powerful API such as those offered by YouTube, FaceBook, Twitter, Google Apps and Vimeo, then you have to use something a bit more powerful.įortunately, for FileMaker developers, we have a number of possibilities. While the basics are always nice to have, you can’t do much beyond access public services with what FileMaker provides natively. Later down the road, FileMaker added in support for the POST method of service interaction with the httpspost:// url scheme. When it comes to FileMaker, you’ve always been able to do super basic REST with the Insert from URL script step. Before it, came SOAP and XMLRPC, but the two buzzwords you’ll hear over and over these days are REST and JSON. REST (Representational state transfer) has quickly become the de facto standard for communication between services and apps. ![]()
0 Comments
Read More
Leave a Reply. |