Combining functions, features, or steps in creative new ways can deliver productive results. I was thrilled to discover in FileMaker 18 that the new file-based script steps give us the ability to perform imports natively on FileMaker Server, with no configuration or changes needed.
Well, here we are again! With the release of FileMaker 18 we get the third version of the FileMaker Data API. This version brings an iterative advancement in features while maintaining the core functionality that was introduced with V1 of the API in FileMaker Server 17.
NOTE: We’ve updated this series of blog posts and demo files to cover FileMaker 19:
“Hey Siri…Ask FileMaker…”
This story started when we explored iOS Shortcuts to the FileMaker Data API. As we continue to automate tasks by mixing together iOS apps, content on mobile devices and web APIs plus FileMaker, let’s add to our workflow using one of the most powerful functions available to iPhone and iPad users: Siri.
Introducing Admin FM – the Zapier integration for accessing the FileMaker ® Admin API in an easy, customizable way. Built using Node.js, this version of Admin FM is currently a beta version, but it allows you to access most of the functionality that the FileMaker Admin API allows.
We support quite a few macOS systems that are bound to an AD (Active Directory) domain. Occasionally, one, two, or perhaps several would lose the ability to authenticate users with AD credentials. Often this was with one of the FileMaker Servers, where external authentication was being used for either user access or FMS Admin Console access. I’ve explored ways to fix this, without restarting or disrupting other services.
Now that the FileMaker Data API has been officially released (with FileMaker 17), it is time to share an update on Tableau-to-FileMaker integration. I originally wrote about integrating Tableau and FileMaker to create a match made in data heaven. I’ll also be speaking on “FileMaker + Tableau” at FileMaker DevCon 2018.
If you have a FileMaker server that you want to ensure high availability, Amazon’s AWS Route 53 service has some functionality that you’ll want to know about. For this post, I’m going to show how you can set up monitoring and alarms for the XML interface on FileMaker Server.
I’m always excited each time the FileMaker Platform gets new capabilities. It isn’t just the new features on their own that make things interesting, but what happens to the platform as a whole which provides for some interesting and inspiring innovations. In this case, it is a new way to do transactional record editing in FileMaker. This is the first in a multi-part series on this topic.
Continue reading “How Transactional is the FileMaker Data API?”
As y’all probably know by now, FileMaker 17 has been released, including the first production edition of FileMaker Server’s Data API. This API was originally released with FileMaker 16, but only as a “beta”, expiring September 2018. As you might expect, the FileMaker 17 Data API introduces significant changes. This means that any applications written against the FM 16 Data API need to be refactored for compatibility with FileMaker 17. And that’s the work we’re here to do!
Continue reading “Using REST and cURL with FileMaker 17’s Data API”
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.
In addition to the more typical external authentication methods, FileMaker supports client authentication using OAuth accounts from Google, Amazon, and Microsoft. In this instance, I needed to set up a FileMaker Cloud server to use a company’s directory accounts, which were hosted at Azure. In order to set this up I hit a couple of minor complications, which I’m going to cover here.
I needed to set up some monitoring for FileMaker Server that made moderately heavy use of the XML interface for Custom Web Publishing (CWP). The server was mostly working well, but was due for a rebuild, or at the least, an upgrade, but the client wanted to squeeze out one more season before we did this.
Continue reading “Monitoring FileMaker’s CWP Connectivity”
In looking back at our initial approach to logging FileMaker PSoS (Perform Script on Server) activity, I reflect back on a number of times where this has been extremely helpful. If you have come to rely on the benefits of PSoS then you also know some of its challenges — one of the biggest is debugging and monitoring how long sessions take.
Since FileMaker 16 introduced JSON, in new systems we’ve switched over to using JSON as the main way of exchanging data for parameters. Because we also use PSoS in new systems, we updated our method for PSoS Logging and this blog entry talks about the changes we made there and also restates the usefulness of this log.
Continue reading “Logging PSoS Activity: Episode III – Return of the JSON”
FileMaker 16 has been out for several months, however we wanted to call attention to a change that can effect your application’s use of server side scripting. Recently, we upgraded a client project to FileMaker Server 16, and found that critical functionality had mysteriously broken. After a bit of sleuthing and gnashing of teeth, we found that changes to the output of
Get(SystemDrive), when executed server-side (PSOS or via a scheduled script), was the culprit.
Apple’s macOS Server 5.x has a rather different Apache configuration compared to the core macOS setup or those used in previous versions of Server. In particular, an instance of Apache is used as a proxy to any ‘backend’ copies of Apache. Here’s how to work around this…
If you are FileMaker developer, but new to the notion of web APIs and web development in general, then you might take on a kind of deer-in-the-headlights look when confronted with FileMaker Server 16’s new Data API, aka “REST API”. Fear Not! It really is simpler and more straightforward than you might expect. I like to take the attitude that no skill is difficult, only unfamiliar. With study and repetitive exposure and practice, any skill can be mastered.
Since FileMaker Server version 13, FMS has used its own Apache configuration files on macOS instead of just adding includes to the OS configuration files. Because of this, the technique I mentioned here no longer works for newer systems. This new arrangement has reduced issues for FileMaker Server’s web connectivity.
If you’ve installed the FileMaker Pro client using a “For Teams” license, or as part of your FileMaker Cloud server usage, you may see a new dialog in FileMaker Pro.
In version 15, FileMaker has introduced a a new user-based licensing model. With FileMaker for Teams and FileMaker Cloud, a license allows use of Server and Client software based on the number of subscribed users.
Optimized for FileMaker 15, the new version of bBox includes 160 examples
We are pleased to release another update to bBox, v0.84 of our free utility plug-in to extend FileMaker solutions to other programs, code libraries, and OS X functions including Python, Ruby, AppleScript, Perl, Bash/sh, XPath, and SQLite.