Better UI Settings

Longtime FileMaker developers have often used the database itself to store values for various user interface settings. This is valid, because, where else would you store them? A common approach is individual fields. However, there are a few problems with this.

First, it adds "noise" to your data structure, making it harder to distinguish between actual data fields and those used for other purposes. For example, you might ask, "Is this an actual data field or is it used for something else?"

Second, FileMaker’s data transfer over the network is essentially all or nothing because every field in a table must be transferred. I've seen solutions with literally thousands of fields - every one of them, and their contents, is being sent over the wire.

This is not an ideal situation, but it can be easily mitigated by migrating to a system that addresses both issues. Furthermore, you can take additional steps to move this data just one table away and still maintain the same benefits for your user interface.

This video presents a modern approach to managing your user interface settings. By learning from it, you may also gain insights into other ways to use JSON in your development.

Click the title or link to this article to view the video.

View the full article