This user only has access to the Data API layout and to modify the four geolocation fields.
The remainder of the layout consists of FileMaker fields. The WebDirect layout has a webviewer at the top with a the single button that is conditionally formatted based on the record state (never checked in, currently checked in, or checked out). It contains two layouts: one is for WebDirect and the other is for the Data API. geolocation.fmp12 – FileMaker database to host on FileMaker Server.The webviewer in the FileMaker file references the HTML page and has parameters that are passed in like the FileMaker recordID, as well as values that may have already been recorded in the geolocation fields. If you want a serverless solution, you could skip the PHP/server-side matter altogether and just have your JavaScript function to make a call to some REST API that would do the heavy lifting of writing back to FileMaker Server. For an all-in-one standalone solutions, enabling PHP on FileMaker Server gives us an easy win. At Proof, we generally prefer AWS Lambdas APIs or Claris Connect to glue our workflows together.
If being entirely standalone isn’t a requirement, you could use something other than PHP to serve up the HTML/JavaScript file.
FILEMAKER SERVER WEBDIRECT CODE
We add a little JavaScript code to get coordinates using the HTML GeoLocation API and send them along with the FileMaker recordID to a PHP page, which then makes a REST API call to FileMaker Server via the Data API. To start, we have a FileMaker file that references a basic HTML page containing a single button that is conditionally formattedīased on the record state (never checked in, currently checked in, or checked out). (Stay tuned for a FileMaker 19 version of this solution.) For now, the constraints that gave rise to this solution are that (1) we have a FileMaker Server 18 hosted WebDirect solution and (2) we want to avoid plugins or other technologies that are not directly supported by However, in FileMaker 18 or earlier, there is no built-in way for us to get geolocation data out of the webviewer and back to FileMaker. HTML5’s GeoLocation API gives us a web-native way of doing this within the webviewer. In this article, we will be looking at a demo of a check-in/check-out system based on geolocation that is specifically for FileMaker WebDirect clients.
0 kommentar(er)
