ISO FileMaker Magazine

Capturing external data directly into FileMaker has always been a bit of challenge due to the variety of technologies required to set everything up. In the past, XML and PHP were commonly used, taking advantage of direct integrations available in FileMaker Server. Even earlier, during the "wild west" days of FileMaker, some systems remarkably relied on AppleScript to facilitate data exchange. Claris, then operating as FileMaker, Inc., provided libraries and methods to enable these connections.

Over time, the rise of JavaScript introduced Node.js, which FileMaker Server eventually adopted for certain functionalities. This led to the introduction of the FileMaker Data API, which allowed developers to use RESTful methods to interact with FileMaker databases, enabling data to be sent and retrieved efficiently. But this came with more required know-how and often times an additional server setup.

FileMaker Server lacked both a simple and straightforward way to exchange data using a simple shared key - such as an account password. Additionally, using the Data API required using the ever-present contextual data map known as the Relationship Graph. The Data API relies on Layouts for data retrieval and manipulation.

The introduction of OData support significantly changed the game. If you’re looking to exchange data with your FileMaker database via services like Google Forms, AWS Lambda scripts or others, this is the technology to learn. When combined with the potential for serverless architecture, new possibilities emerge. This article’s accompanying video and JavaScript code will show you how to use a simple Google Form to capture data directly into your hosted FileMaker database.