ISO FileMaker Magazine

Using multiple files for developing a robust FileMaker solution can be pretty normal when you plan out the distribution of your data and servers. Some solutions benefit from breaking out part of the solution into one or more separate files.

So, whether taking the load off a given server or simply planning for quicker data access across multiple time zones, one of the bigger problems which pops up with your standard FileMaker accounts is password management. This is where it becomes much easier to use external authentication.

In earlier days, we only had access to Active/Open Directory or system accounts hosted on the same machine as FileMaker server. But, since FileMaker Server 16, we now have the ability to use external authentication through Oauth. This means we can use a third party like Amazon, Google or Microsoft in order to allow users to access solutions and manage their own passwords.

If you're looking for an easier way to manage the users of your solution, then you'll find out how it works and how to make it happen within this video about Oauth External Authentication.

One of the challenges I love the most within FileMaker is creating something which requires less time and effort than the "older way" of doing the same thing.

Such is the case with a tabbed list view. I recently came upon a sample file showcasing how to do something in multiple list views. It was using an older method of "simulated" tabs by simply placing clickable buttons in a horizontal row and making one of the buttons look different on each respective layout.

So I thought to myself, "Why isn't he just using a normal tab panel?". You can certainly do it. You just need a few key pieces of info in order to create a very powerful navigational tool for a tabbed based list view. And, that's what this video is all about Tabbed List Views.

Every software user loves convenience. Heck, every human being loves convenience. So, why not provide it within every aspect of your user interface?

The problem, however, which you may run across is figuring certain features out. FileMaker can be a very simple program or something quite complex if you're trying to do something custom like providing users with the ability to custom order their related records.

The most basic sequential ordering of data comes in the form of simply providing a number field called something like "order", "sequence" or the more mathematically inclined "delta". Once you have the field, you can allow the user to manually change the values. But, that becomes a real pain when you try to add a record between the numbers 1 and 2. You now have a user entering 1.5 or 1.3 and 1.7 in order to get values to sort properly. Then, having to manually reserialize all the original values is just an unnecessary pain.

Well, the best solution to this problem is to simply use the automation provided by FileMaker's powerful scripting engine. With a few scripts, a value list, and a bit of FileMaker know-how, we can provide a very quick-and-easy method of allowing users to custom order portal rows.

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.