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 kommentar(er)
