



In the above example, the field contents are not valid JSON due to the accidental placement of a semicolon after the “ddd” element. This simple test will determine whether or not the contents of that field are indeed valid JSON. …and that field contains something that looks like it might be valid JSON. Specifically, if you point JSONGetElementType at a JSON structure, or at an element within a JSON structure, it will return the corresponding type in numeric format.įor example let’s assume we have a field called “source” in a table called “sandbox”… Over the years developers have come up with clever tricks to address both of these needs, but good news, we can now ditch the clever trickery because JSONGetElementType removes the guesswork. Have you ever wished that FileMaker could target an element within a JSON structure and return the type (JSONNumber, JSONString, JSONObject, etc.)? For that matter, have you ever wished for a simple way to determine whether a block of text is valid JSON or not? FileMaker Pro 19.5 FeaturesįileMaker Pro client has several new features, including: JSONGetElementType ( json keyOrIndexOrPath ) Let’s take a look at what Claris FileMaker has to 19.5 offer. It builds on their open platform promise – introduced in FileMaker 19 – and strengthens the platform’s performance, security, and reliability. We now have the highly anticipated release of FileMaker 19.5! This article intends to share the highlights of new features, deep dive into a couple of examples and share some important news regarding bug fixes across the various platforms (FileMaker Pro, Server, and WebDirect).įileMaker 19.5 is Claris’ strongest release to date.
