![]() ![]() 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. ConvertFromFileMakerPath ( $filemakerPath PosixPath ) //Convert FileMaker to Mac/Linux Plugin PathĬonvertFromFileMakerPath ( $filemakerPath WinPath ) //Convert FileMaker to Windows Plugin PathĬonvertToFileMakerPath ( $pluginPath PosixPath ) //Convert Mac/Linux Plugin Path to file://Mac path.ĬonvertToFileMakerPath ( $pluginPath WinPath ) //Convert Windows Plugin Path to file://Windows path.REST (Representational state transfer) has quickly become the de facto standard for communication between services and apps. A "plugin" path is the same as the PosixPath for Mac or Linux, and the WinPath for windows operating systems. The best way to convert paths is to use the native FileMaker functions ConvertFromFileMakerPath and ConvertToFileMakerPath. Note the consistency of the type of slash used, vs the difference in \ vs / in Windows/Mac. Windows : file:///C:/Users/John%20Smith/Documents/test.xlsx FileMaker Path Examples Mac : file:///Volumes/Clients/contacts.txt You can then adjust this path to suit whatever location you need, or to get an example of the difference between selecting a file on the desktop and running the Get ( DesktopFolder ) function. This will return an example of the sort of path used by the function. To get an example of the sorts of paths that the plugin uses, use the BE_SelectFile function in the Data Viewer, and choose a file with a known path. Windows : C:\Users\John Smith\Documents\test.xlsx Plugin Paths Examples Mac : /Users/John Smith/Documents/test.xlsx" So if you're mixing and matching FileMaker paths and plugin paths, you will need to convert them between the types in order to use them in other places. These file: prefixes that you get from things like the Get ( FilePath ) function and others, are unique to FileMaker and don't work anywhere else other than FileMaker itself, including not in the BE plugin. On the Mac, they usually start with /Volumes or /Users and on windows will be something like C:\Folder\Path.įileMaker paths often start with file: or filemac: and these WILL NOT work in the plugin. The paths used by the plugin are Operating System paths. ![]() Please note :įileMaker paths and plugin paths are not the same thing. Lots of the BE plugin functions use paths in the parameters or in values they return. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |