ISO FileMaker Magazine

One of the fundamental methods for loading a found set of records in FileMaker has traditionally been storing and using the key values of a selected set of records. With the powerful Go To Related Record script step, you can easily load any number of records.

This can be achieved through either a global field relationship or a standard schema relationship. However, with the established method, if you want to store and reload a found set, you need a few additional elements: a Summary field (low overhead) and a dedicated relationship, which is always going to be required.

With the introduction of the new GetRecordIDsFromFoundSet() function in FileMaker 2025 (v22), this process becomes significantly easier.

Whether you’re recreating a simple found set or reconstructing a complex query using record ranges, this new function will help you streamline your solutions and reduce development overhead.

Aside from the welcome user interface refresh in FileMaker 2025, a valuable enhancement has been made to the existing grouping feature. This update encourages greater use of grouped layout objects and helps reduce the number of layout-based calculations, a point of frustration with the previous limitation.

Prior to FileMaker 22, if you applied either a button action (now discouraged) or a hide calculation, you had to ungroup the object before adding anything new to the group. This often caused problems: if you forgot to copy the calculation before ungrouping, you risked losing it and then had to reapply it after regrouping.

With the new enhancement, you can now add or remove elements from a group in multiple ways with no ungrouping required. This short video will walk you through the feature in detail.

One of the powerful new features in recent versions of FileMaker Pro is the Open Quickly feature. While it initially had issues with giving users too much access, those concerns have been resolved through updated privilege settings.

In this short video, I focus on a few things you can do with the Open Quickly feature. From jumping to fields several tables away to managing multiple layouts while working on your design, adopting the Open Quickly feature can significantly speed up your development process.

Breaking down complex logic into manageable chunks of code is the smartest thing you can do when it comes to conditional formatting. Especially when it needs to account for an increasingly wider number of conditions.

This week's video deals with what seems like a simple solution to solve, yet it comes with all kinds of complex little pieces to make the solution provide the end result desired.

If you enjoy the type of video which is a bit of a solution walk-thru, where I discuss how things are solved, then make sure to spend a bit of time with this technique and video.

When tackling the task of updating a UI/UX look and feel, it can quickly become overwhelming — especially if you have hundreds of layouts and countless individual styles, some in use and others deprecated.

While designing a new solution from scratch allows you to take advantage of modern best practices, many existing solutions have simply relied on the Default style and applied it across numerous layouts.

The goal of this video is to demonstrate how you can achieve an updated look without disrupting the existing one. If you recognize that style names are the key and plan for the migration, you can accomplish several objectives:

1. Eliminate the use of the Default style in your UI.
2. Remove or transition outdated styles that are no longer in use.
3. Most importantly, establish a consolidated theme where the Default style can serve as a single control point for making sweeping, solution-wide changes with minimal effort.

Taking the time to phase out the Default style and integrate an updated theme can also inspire the use of newer UX tools and techniques that have emerged in recent years.

Every development task involves both what you know and what you don’t. The key to achieving the desired outcome often lies in learning what you don’t yet understand. That’s exactly what we’ll explore in this video – how to collect data from related tables for use in various ways.

If you haven’t used the GetNthRecord() function before, this video provides a perfect example of one of its applications. When combined with the While() function, you can build virtually any data structure to help you achieve your desired solution.

Designing layouts in FileMaker is one of my favorite aspects of the platform. The ability to simply drag and position elements exactly where you want them feels akin to being a painter, free to use any tools and materials you choose. FileMaker strikes a remarkable balance between the creative and technical sides of development.

Like all things, achieving the desired results requires knowing a few tricks. Whether it's about stacking objects efficiently or minimizing their number, it's up to the designer or developer to bring the vision to life.

In this video, I showcase a few adjustments I made to an example file I downloaded. This file, likely created to explore the newer OData technology, provided an excellent opportunity for me to demonstrate how I approach the UI design of a FileMaker layout. I also share how you can make a few small tweaks that might improve the overall maintainability of your solutions.

When incorporating graphic design into your FileMaker solution, you might either be the sole designer or collaborate with someone to enhance the user experience. Regardless of your role, it's always beneficial to understand how to effectively use colors within your solution.

You can, obviously, make straightforward choices, such as simple selections of colors from the built-in color picker. But, there are additional tips and techniques that can significantly enhance your ability to use colors strategically, helping you achieve your ultimate design goals.

Whatever your objectives may be, understanding the best practices for selecting, applying, and implementing colors in your FileMaker solution is essential.

As technology advances and becomes as critical to our digital lives as water is to our physical well-being, we must be keenly aware of whether that "water" is tainted with harmful elements that could harm us.

This sentiment applies not only to your health but also to your technological security concerns. For most technical systems, we may be inclined to assume that "big tech" — meaning the creators of the software or technology — will automatically make things safe for us. However, there may be risks that neither the provider nor the user recognizes until they surface.

Recently, the FileMaker landscape has been impacted by several critical security findings, making it essential for you to understand your level of exposure.

In many cases, threats may be mitigated by measures within your control. However, in some instances, upgrading is the only viable solution. Many FileMaker systems still rely on versions much older than FileMaker 19, following the old adage, "If it isn’t broken, don’t fix it." This time, however, it is very, very broken. Older versions of FileMaker Server, if publicly accessible, can be hacked in ways that conceal any traces of intrusion. In this case, using outdated versions is a risk you can't afford unless you're prepared to accept that your system is essentially open to anyone willing to find it.

Be sure to use the link below if you're interested in purchasing! There may be unexpired discount codes available.

Being more productive when developing in FileMaker is something that will always pay off. You’ll create solutions faster and feel better about how quickly you can solve problems.

Due to the unique environment in which we write code, there are concepts other developers have access to that we don’t. We’re not using a standard text editor with modules and plug-ins to extend its functionality. In FileMaker, we rely on a few third-party plug-ins and tools to enhance the development experience.

In this video, I’ve invited Robert Naud and Josh Halpern to demonstrate Typinator from Ergonis Software. It’s a powerful tool that can handle all sorts of tasks involving the OS clipboard and FileMaker. Since FileMaker uses a dedicated clipboard format, which is primarily XML, you need to translate that XML into the normal text you work with. Typinator makes this possible. You can automatically inject script steps, layout objects, custom functions, and almost anything transferable via the clipboard. By combining AppleScript and/or JavaScript with a few command line tools, you can work in FileMaker with auto-expansions that make your job much easier!