ISO FileMaker Magazine

If you don't pay close attention to the fields you add to your record load in Claris/FileMaker, you might end up facing a transfer penalty, especially when dealing with container data. In many cases, your end users may not require the data from heavy multi-megabyte container fields. Nevertheless, every time the record data is loaded, that large container data gets included as part of the transfer.

Unlike SQL or a document database, where you can request only the necessary data, FileMaker provides the entire record, including all field data. Therefore, it is essential to create a structure which optimizes the utilization of containers. While I have previously covered this topic, this video offers a walk-through experience as I demonstrate how to implement support for a singular Files table, which can be used in multiple locations across a solution. I also discuss various options, such as one-to-one, one-to-many, and many-to-many relationships, when it comes to loading associated file data.

If you have ever wondered how to further enhance the speed and performance of your FileMaker solution, this video provides valuable insights into how you should likely structure your use of container fields. Understanding the concepts covered in this video will likely improve the performance of your solutions.

Being able to develop and test your solutions within a FileMaker Server environment is the ideal scenario. You can test Perform Script On Server, external binaries, and plug-ins that perform a variety of tasks. Essentially, you can perform all the necessary tasks in a real solution.

When you develop your FileMaker solution locally with a single copy of Claris/FileMaker Pro, you not only face limitations in what you can test but also risk the possibility of a crash. While running FileMaker Server on your local machine is a satisfactory solution, the next step is being able to run multiple versions of FileMaker Server without the need for multiple uninstall/install scenarios.

This video showcases my return to using Docker Desktop on an M1 Mac Studio ARM-based machine. Previously, I had to stop using Docker and resort to a full virtual machine when I switched to using Apple Silicon. However, with the release of an ARM-based version of FileMaker Server and most plug-ins being available for the ARM architecture, we are now able to use Docker Desktop again. The trick lies in learning how to use containers. This video provides a great opportunity to learn a new skill. If you want to run multiple variations of FileMaker Server on your M1 or M2 Mac, this video has what you need.

While learning to develop within any environment, it's common to develop habits which keep you within a consistent framework. However, occasionally looking outside of your current framework and observing how others accomplish similar tasks can be both affirming and instructive. You may discover valuable tips and tricks from other developers from which you can adapt to enhance your own practices.

This video focuses on script writing and explores various techniques employed by different developers, specifically regarding the documentation and structure of scripts. By examining multiple files and exploring different scripting methods, we can gather helpful insights. Additionally, I will present what I consider to be one of the best approaches to managing a complex script that utilizes multiple inputs and outputs.

The beauty of Claris/FileMaker is that you have the flexibility of keeping things simple or making them as complex as desired. Drawing from my decades of experience, this video offers numerous tips to improve your script writing skills. You're likely to find valuable insights that can elevate your approach to scripting.

While Claris/FileMaker offers a convenient Duplicate Record menu option, of which there's always a companion script step for most menus, there's more to the equation than simply duplicating your primary record. In fact, in most situations, it is necessary to duplicate both parent and related child records. You will likely need to duplicate a complete set of records to address the entire entity. For example, think of the relationship between Order, Line Items, Ship Address, and so on, in order for a customer to place a duplicate order.

To accomplish this, there are various native methods available, often involving multiple GTRR (Go to Related Record) steps. Additionally, within your script, you will need to carry a newly created primary key to all the newly created child records. Therefore, the question arises: "What happens when you need to duplicate a large number of record sets?" This was the question posed by Daniel Wood, who proceeded to test and document the methods and their benchmarked results in an article published on their blog at the FileMaker consultancy Digital Fusion.

When confronting this same question, there is a method that I personally favor and know to be quite fast, and I was eager to see how it would perform. I integrated this method into Daniel's file and discovered that by utilizing a plug-in, a significant speedup can be achieved. This article focuses on the fundamentals of how this technique works and provides guidance on its implementation in your own solutions. I'd like to express my gratitude to Daniel for his hard work and for granting permission to distribute a modified version of his file.