I am increasingly fond of the idea that FileMaker should support JSON as a native column type. FileMaker text fields already allow storage of massive amounts of text so the precedent of loading up a table with JSON objects in columns doesn't seem like too big of a stretch.
While it is certainly possible to store JSON in a text field today, I am suggesting that we have:
- a field type that can be validated as a JSON
- the ability to then map or bind layout objects such as fields and portals to JSON "fields; i.e.create fields/portals that correspond to JSON objects types and store/update the stored JSON data
- new UI controls such as tree views that can natively mapped to this JSON field
...imagine the possibilities
see also, JSON as a data source object