ISO FileMaker Magazine

When you first start writing scripts within FileMaker, you're typically so focused on the feature or solution you're working on that you integrate it directly into the area where you're working.

It takes a bit of time and skill, however, to quickly recognize when you need to make a particular script more generalized in nature and treat it like a routine which simply needs to take input and provide some output.

Once you get to this point in your development path, you discover all kinds of opportunities where one script will serve the purpose of many. And, you may find that some of your scripts are in the range of 80 to 90 percent redundant. Possibly varying by only a few lines of code.

In this video, I present a very common pattern for many scripts. Treating them like a function and simply following a format for inbound and outbound data from that script. You'll also find a good number of tips regarding documentation, script composition and the big bonus is that we do this with a script which will give you the instant ability to send out text messages via the Twilio API!

While many FileMaker solutions will manage multiple parameter passing in very simple and straight-forward ways, there are some solutions which you know will grow over time. Because of this expected growth, you may want to have an additional level of comfort knowing you've implemented a very strict system for managing data transfer between scripts.

You also may be interested in working with external APIs and connecting to systems and data which is provided via the currently popular format of JSON (JavaScript Object Notation).

Since the release of FileMaker 16, we've had access to the fundamental JSON* functions. With their initial release, there were a number of developers who immediately jumped on the bandwagon. Since FileMaker 16 was released, we've had a good bit of time to codify some methods and helpful custom functions for working with JSON formatted data.

This video is all about providing comprehensive initial coverage about how JSON can be used for passing multiple parameters within FileMaker. If you never quite taken the plunge into using JSON for parameter passing then this video and the associated file may very well provide you with the incentive to take a more serious look. At the very least, you'll know what's going on when other developers mention they're using JSON parameters!

Every craftsman should know how to use his or her set of tools effectively. When you know all the various uses and features of a given tool you then become more efficient at your trade.

In FileMaker Pro Advanced, now available to pretty much everyone in version 17, there's one tool which helps you both understand what's happening and figure out what's not happening. The Script Debugger is an absolutely essential tool.

Creating a well functioning script is a lot like Michelangelo creating David. It didn't just appear because he held the tools in his hands. It was because of the constant refinement with the tools until the beauty within was finally present. Writing a script is no different. You won't get it right the first time and you with almost always be able to refine and make it better.

So, it goes without saying that knowing how to use the Script Debugger is one of the number one things you should know how to do when coding in FileMaker Pro.

The ingenuity of developers has always extended beyond the limitations presented within any given environment - both physical and virtual. If you can't cross a river with your cart and horse, then you learn how to build a bridge and make it last.

Such is the case with FileMaker's script parameters. There's always been only one way to pass anything into a script - as one big blob of text. There's nothing which controls what type of data is embedded within the block of text and it's up to the developer to create a method for passing discrete pieces of data. From the most basic method of simply passing a return delimited list of data we can always take the individual pieces one by one from the list.

Things, however, can get a bit more complex with larger amounts of data. When you need to pass return delimited data as a single parameter out of many you have to be a bit more creative. This is where FileMaker's addition of its JSON functions within FileMaker 16 have helped moved the feature set forward. While there is no native methods for passing multiple parameters, we do have a standard structure for name/value pairs now when working with FileMaker.

When it comes time to “professionalize” your FileMaker solution, this typically includes integrating a splash screen. Even if your solution is only used internally, that extra bit of branding solidifies that mental spot of recall when a user needs to communicate which database they’re using.

So what better way to say “You are here” than presenting a nice, attractive splash screen? In this video, I walk through the step-by-step process of adding a cool-looking splash screen to our ongoing project of the Custom Function database.

In the process of doing so, I explain a variety of other reasons as to why I choose the method showcased in the video. It’s more than just the pretty picture which shows on startup. It deals with startup speed and other helpful features such as increased security potential. If you’re going to put your best foot forward, then follow the method shown in this video!

This video will teach you all about using the new FileMaker 16 Card Window and show you how to take advantage of the fact that you can have a totally different position for the card window outside of the parent which where it belongs.

With a bit of creative FileMaker scripting you can create some really nice features for your FileMaker database.

While it would be wonderful if FileMaker Pro had built-in functionality for all of the features we can possibly think up, it’s not too practical. Besides, what would be left for us to develop?

So, what about saving user state? Do you think you would enjoy leaving your desk for a few moments and coming back to a completely rearranged environment? I doubt it, and that’s almost exactly what FileMaker does when working within a hosted file.

The most common approach to solving this problem is to simply provide a “directory like” structure. Like walking into a mall and heading to the directory map in order to find out where you can possibly go. Call it what you like, a dashboard, main navigation, whatever. You’re simply reseting the user each time they leave and come back into the software.

Well, if you’d like to take another approach, then all you need to do is save the user’s last know state. What you save and how you return the user to their last known state is in your full control. It’s not that hard to do and this video will give you all the details you need to know.

Learning how to efficiently create scripts within FileMaker is a never ending process. It's a balance of leveraging what you know and mixing in newly added features along with new ways of doing things. Optimization and cleanup will always be part of the ever growing software solution.

In this video, I present the topic of using utility scripts in order to save precious development time. You know, those reusable scripts which prevent you from writing unique and dedicated scripts for every possible scenario in which the user will interact with your solution.

They're the scripts which end up saving you a ton of time and get used over and over again. They can be used stand-alone or they can be called by other scripts. But, no matter how they are used, it's certain they are valuable pieces of reusable code.

If saving time and reducing the number of scripts you write is of any interest, then this video will have the information you need.