We have better tools than ever in FileMaker to create reusable modules. In this video of Mark Scott’s presentation at a Bay Area FileMaker developer meetup, he explores why the combination of card windows and JSON reigns supreme for modular FileMaker architecture. Included is an in-depth look at how modules can open, close, and communicate.
Changes in FMS 17 Admin Console and How We’re Adapting
FileMaker Server 17 introduces a new generation of Admin Console, refreshed, fast, and reliable. If you are familiar with the FileMaker Cloud console, you’ll feel right at home in the new FileMaker Server 17 Admin Console. However, the update also brings some of the biggest changes in administrative functionality in years, perhaps ever.
While FileMaker provides an excellent overview of the differences, here I will highlight changes that affect us most here at Beezwax and some adjustments we’re making to compensate.
FileMaker 17’s new master-detail layouts display the list of records in the user’s found set. As the user performs finds, constrains, omits, sorts, or creates or deletes records, the master-detail portal will update to stay in sync. Imagine a portal that a user can sort any way they like, filter any way they like, and click a row to see details for that row, all right out of the box. That’s the power of the master-detail portal.
Last year when I wrote this blog post we were talking about FileMaker 16 and the Data API being in beta. Now that FileMaker 17 has officially been released and along with it the Data API is out of beta and is a version 1.0.