FileMaker 19 introduced some game changing functionality to the platform, including the JavaScript functions and Add-Ons. Another last-minute feature that made it into the release was the Execute FileMaker Data API script step. Documentation is sparse at this time, so we set out to find out what it does and how it works. Let's jump in...
More and more online services are utilizing webhooks as a resource-light way to respond to an event, often times pushing around some data. So if we as FileMaker developers want to take advantage of these webhooks, how can we go about it? Well, dig in and find out!
In the process of setting up a machine for a client recently, we encountered an issue where FileMaker Pro 19 was installed, with the license certificate in the downloads folder as it should be, but we were asked for the license certificate each time the app was launched. And when it did launch, the app was in trial mode with an expiration date. But wait, we have a valid license...
The JSON functions were introduced in FileMaker 16 and since then, as it's native functionality, we've used these functions for passing around data in script parameters and more. Often times, we'll be, say, clicking a button on a layout and passing multiple JSON formatted script parameters to the script being executed. But we began wondering if there was a quicker way of extracting the parameters into variables in the script, and it turns out there is…
It’s not uncommon, as a FileMaker database begins to grow, that the volume originally set up on an AWS instance begins to run out of space. To tackle this, you could launch a new instance with a larger volume, but that seems like a bunch of work and there’s a much simpler way of solving this problem. Let’s find out how…
If you upgrade your Mac server to macOS 10.15 Catalina, you might find that your backup schedules to external drives start failing with an error number 156. Although apparently fixed in FileMaker 18.0.4, it's rearing its head again, but there is a simple fix.
Custom default fields were introduced in FileMaker 17 and proved to be immensely useful. The functionality allows for the automatic creation of fields when making a new table, ensuring consistency for fields like primary keys or creation/modification timestamps for example. If you had set this up in 17, when FileMaker 18 was released, they continued to work. But try it with FileMaker 19 and your custom default fields are gone. Don't panic, it's a pretty simple fix.
FileMaker Pro 19 is now available, and with the release come a bunch of awesome new features to further enhance the capabilities of the platform. In this post we’ll check out, in brief, some of the key new features and in further posts we’ll dig into a select few a bit deeper.
FileMaker can do literally almost anything, including interacting with APIs. For example, in our previous articles introducing Claris Connect, we've been adding a member to a Mailchimp list. But that process of communicating with the API may not always be so easy. If only there were a way to trigger a Claris Connect flow from within FileMaker. Oh. Wait. There is! Let's see how...
In our previous articles introducing Claris Connect, we've been integrating cloud based services to handle a particular workflow. But we're FileMaker developers at heart. So how does our database fit into all this?
Well, we're glad you asked, because the answer is pretty darn well! With FileMaker also being a Claris product, those clever folks over there made sure that FileMaker could be used within a flow of Claris Connect. So let's send some data from our flow to a hosted FileMaker database.
Sounds Essential LLC
PO Box 2229
Cashiers, NC 28717
t. 828-743-8350
e. info@soundsessential.com
We occasionally send out news of general interest in our fields of specialty. Sign up to stay up to date.
© 2022 Sounds Essential LLC. All rights reserved.
