ISO FileMaker Magazine

Some developers who start with FileMaker never extend beyond it. Hopefully, that's not you. Or, at least you're willing to look into learning some other languages and see how they can benefit your FileMaker solutions!

In FileMaker 19 we gained both a new script step named "Perform JavaScript in Web Viewer" and a JavaScript function embedded into the Web Viewer named "FileMaker.PerformScript()". If you haven't taken the time to investigate how these new features work, then allow me to give you the gentle push into taking advantage of them.

While formerly we could use a plug-in to directly execute JavaScript, and there were some "hackish" workarounds to using the JavaScript within Web Viewers, we now have a totally native way to take advantage of this very powerful technology. Understanding how things work, and what you can do, will expand your development capabilities. I highly suggest you take a serious look at learning a bit of JavaScript and the cool thing is you can do it right within a FileMaker file!

Portals and list views represent one of the biggest reasons for using a database for managing data. You can view the data in a myriad of ways and FileMaker provides the tools to modify the views quite easily.

FileMaker's list view happens to be the most powerful when compared to portals. We don't really have the same feature set presented within a portal. Using a portal it's an all or nothing approach to sorting by default and you can't really search the portal contents. You can certainly hack in some method of controlling the sort and the old standby of simply adding new copies of the same portal, just sorted in different directions, has always been a go-to workaround.

Well, has the time come to simply abandon your portals? What?!?!! Abandon portals? Is that even possible in FileMaker?

Actually, it is, with what FileMaker now offers with bi-directional support within Web Viewers, it may be more viable than you've ever considered. In this two part video series I show you exactly how easy it is to simply retrieve some data, then present that data within a web viewer. Essentially, replicating a portal - except for the constant data connection.

In many ways, this has become a prime opportunity to choose either a portal or web viewer. The days of always using a portal may have come to an end. But, I'll let the video speak for itself and you can choose if you want to leave your portals behind in favor of what can now be done within a web viewer.

Communication amongst solution users is often a desirable feature. While many companies will standardize on generalized options such as Slack, it's not your only option when it comes to messaging within a FileMaker solution.

In the past, there've been a number "FileMaker only" solutions which take advantage of FileMaker's constant polling of the main data store. However, these solutions pale in comparison to what is available today. With the prevalence of super powerful browser-based Javascript solutions, we can simply use a Web Viewer and integrate directly into FileMaker.

The question, however, is which one do you pick and how can you test things out before making your choice? That's what's covered in this video. How you can test out all kinds of different software integrations within FileMaker. Also, how you can determine if FileMaker's Web Viewer can handle what the software is designed to do.

JavaScript, it may sound scary because learning any new technology, which includes so much more than FileMaker, feels like an overwhelming amount of new learning. The great thing is, learning just a few little pieces at a time is the best way to learn - little-by-little. So let's start with just a few little pieces.

In this video, I walk through the basics of how you get started with JavaScript within FileMaker Pro. How it's implemented and how to execute things. The great thing about getting started is once you learn a little bit, you tend to get addicted to learning more about what's possible.

It turns out, when a technology, such as JavaScript, takes off as much as it has, you gain a significant amount of technological leverage. You don't have to spend as much of your own time creating "all the things", you just piece together the "various things" to make the "one thing" which is "your thing"! But, as with all things, you need to know what's going on behind the scenes so you can fix, change or troubleshoot what may not work quite right. Which, seems to be the case with all kinds of software development.