Today we’re going to look at an issue that can crop up in FileMaker JSON processing, and explore some approaches one might take to address this issue. Typically the issue arises with preexisting JSON coming from an API, including, but not limited to, the FM Data and OData APIs.

Demo Files
Note: minimum version to open the files is FM 21, but the examples will run significantly faster in FM 22+.
The Issue
APIs that return data as JSON are sometimes unable to recognize JSON as input, and will pass it as text rather than as an object or array. For example, both of today’s demo files include a text field containing a JSON object (the field name is “json”), and if we retrieve records via the Data API, or via the Execute FileMaker Data API script step, the “json” field data will come back stringified (i.e., as quoted text) as per this close-up detail…



