ISO FileMaker Magazine

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!

InspectorPro 8 offered by Beezwax, and created by Vincenzo Menanno and Brendan Pierce takes advantage of the newer Save a Copy As XML feature of FileMaker. This new version of the "Enhanced DDR" provides great insights into team development and the growth and changes of a FileMaker solution.

In this video Vince walks me through the process of installing InspectorPro 8. The features it provides will be quite valuable to any developer who wants to have a solid understanding of your FileMaker solutions.

DISCOUNT!! Make sure to take advantage of a special offer until the end of 2024 by using the code 'filemakermagazine' (without quotes) if you're heading towards a purchase.

One of FileMaker's most advantageous tools added in recent years is the Button Bar. It was the first way to present dynamic, calculated content directly on the screen. This removed the need for the decades-long practice of adding "yet another unstored calculation field." You can calculate something and render it right on the screen.

Then, in FileMaker 20, we got a new layout object called Layout Calculations. While these now provide the same functionality as a Button Bar, they do so without the overhead of unnecessary behind-the-scenes CSS and other extras. However, they are not fully implemented; they don't update any of their calculation references. While this will eventually be fixed, there are unique uses for Layout Calculations that allow for some really cool features—like Render Fields.

In this video, we take a look at generating temporary images for the purpose of PDF generation, which then cease to exist after the script finishes running. These Render Fields can be 100% dynamic on a record-by-record basis and can display whatever you want using an unstored field to show the result. This allows you to multi-purpose a field for multiple layouts. Let's take a look at what Render Fields can provide for your FileMaker solution.

Expanding on a recently released article about Incredibly Easy Menus, which used a Card Window and showcased minimal use of popovers, I've now created a new dedicated setup specifically for use with popovers. Using this method, you can implement the technique and manage your solution-wide popovers from a single location for code. Solution maintenance becomes vastly simplified with this approach.

Remember, our goal as developers is to create DRY (Don't Repeat Yourself) code. This is exactly what this technique achieves. It creates DRY code for the various popovers you'll be using within your solution.

While some degree of context may apply to your popover menus, you can always account for context within the code and adjust as needed. If all the code is in one place, then your job just got easier.

Companies release new versions of software all the time. One of the issues we may face as developers is that not everything is documented and the "marketing spin" might not provide all the technical details. In this video I showcase how I go about the process by performing and ad hoc discover of some of the new features in the Claris FileMaker 2024 release.

Spreadsheets really suck!... Long live spreadsheets, they're super useful! This simple contradiction, however, is likely a part of our technological lives for the rest of time. Unless AI removes the need for people to directly interact with data, spreadsheets are likely here to stay. And, for good reason. They're actually super useful!

As a software/database developer you need to realize that not everyone intuitively understands the solution you've created. In fact, the learning curve, may just be too painful - at least relative to what they may already know. Most users will tend to default to what they feel comfortable with. In the not so distant past, managing data was actually just words on paper. In fact, there's a word you're probably familiar with, it's 'list' - a very common development term. Yep, we still use lists.

Did you notice that? I referenced the fact that you're developing software and you can't really create software WITHOUT using lists. So, why not simply accommodate users' needs to simply default to using a spreadsheet. You just need a simple way to get the data in and out of your solution. Fortunately, this has all been solved by the tab and comma characters. If your users are using a lot of spreadsheets, then enjoy this video article and the associated technique file as we work with the MBS plug-in's super powerful Matrix.* suite of functions for some super functionality. Let's just Copy/Paste that spreadsheet data into a virtual spreadsheet and manipulate the data to fit our needs.

There's nothing more fraught with errors than allowing a human to enter a long string of digits. Some people are detail oriented and others less so. Who cares if you transpose the seven and zero right? Well, we developers care, that's who. We need things to be user-friendly, fast and exact. That's what you get with barcodes.

Try imagining our modern world without them. It just wouldn't be the same. So, why aren't you using them whenever and wherever you can within FileMaker. Put a barcode on everything. Add them to your documents and scan them to load a specific record. Put them on your assets, add them to your employee badges, go crazy.

While FileMaker offers the very convenient Insert from Device script step for scanning barcodes within FileMaker Go, there's no native implementation for creating barcodes. Over the years, many developers have solved the issue of barcodes in many different ways. You can find plug-ins, simple fonts, FileMaker add-ons (which can be frustrating to modify) and straight-up Custom Functions which will create a barcode. By far, the most straight-forward implementation is going to be the easiest to manage and maintain and, in my opinion, that's using a simple JavaScript library which will create the most optimized format possible - an SVG. That's what this video addresses. The cleanest implementation I can think of. It's both portable and minimalistic. Need to create barcodes? You'll learn all the details in this video.

Global fields in FileMaker Pro are a staple of how you define what your user interface can do. Without global fields, your ability to present variable scenarios of data is almost impossible - or - at least, unrealistic. You would be limited to using calculated fields and/or extra data fields, and this can make things really slow, REALLY quick.

Global fields are the linchpin to makings things work well, as desired and efficiently within your FileMaker UI. Without knowing how to take advantage of global fields, your UI/UX abilities suffer.

In this video, we take a look at some of the most critical uses for global fields for common core functionality. From creating related records, to showing whatever data you need to present, it's critical you take advantage of global fields. There are also situations where your current data model simply won't allow you to present the data you want to show. However, using global fields you can create "temporary" relationships to the data you need to present to the user. This video and technique file will deliver some of the critical know-how.