Have you ever run into issues with PDFs not displaying in FileMaker Pro? Does your interactive container field show a loading bar or empty box when you know the field contains a PDF? I’ve run into this issue in two different environments and found that there can be two different causes. In this blog I’ll share the solutions that worked for me.
This month’s Meetup started off with a demo from Matt Navarre of the newly released fmLog 2.0, a simple yet powerful FileMaker logging system developed by AppWorks. It is now available as a free download from our website.
The group then received a sneak peak of Chris Irvine’s DevCon 2018 presentation, Crypto Building Blocks for FileMaker Developers. Be sure to check out Chris’s session in Dallas the afternoon of August 8th. We look forward to seeing you there!
If you manage multiple instances of FileMaker Server, maintenance would typically be performed by logging in to each via a web browser or running fmsadmin CLI commands. These methods become unwieldy when you need to make the same change or gather the same bit of information across several servers. A seemingly simple task now takes 30 minutes or more with multiple servers. For example, ensuring that servers have enabled the security setting “Host password-protected databases only” is a quick task for the first few servers, but surprisingly time-consuming when checking twenty.
The time-saving solution to administering a fleet of Filemaker Server instances is the Admin API. Prior to 17, the Admin API was only available in FileMaker Cloud. Now, FileMaker Server 17 running on Windows or Mac OS can be administered from any tool capable of generating HTTP requests, including curl, PHP, and Filemaker Pro Advanced. Given a list of server addresses, we can programmatically log in to each server to gather configuration information, close database files, run schedules, and more.