ISO FileMaker Magazine

One of the major challenges that any solution or developer encounters is effectively managing the growth of their solution. As the solution expands, the issue of "dilapidated code" arises. This refers to code that either gets replaced or continues to be used without being updated to leverage the latest enhancements in FileMaker. Consequently, a significant portion of the code may become obsolete over time.

One of the most effective solutions to tackle this problem is the use of utility scripts or code that addresses a wide range of use cases. This video showcases the implementation of a commonly used pattern, namely, obtaining user confirmation to ensure that their intended actions align with the expected outcome. By employing a utility script called "Confirmation Prompt", we can prompt users not only for record deletions but also for various other situations.

This powerful utility script allows us to manage a variety of user interactions, such as setting a temporary $$UI.VARIABLE or modifying the value of a hidden field. Furthermore, the video presents one of the best approaches to learning and utilizing JSON, in case you haven't embarked on that journey yet. JSON proves to be an excellent method for managing serialized data within Claris/FileMaker. If you aim to streamline your solution and reduce the total number of scripts, incorporating the utility script from the provided technique file will undoubtedly save you a significant amount of time.

Sometimes, it's just good to reflect on how you use certain FileMaker features. You know, the simple ones. Like Show Custom Dialog and Get ( LastMessageChoice ). If you use FileMaker for mobile a lot, then Show Custom Dialog is a great way to go. With Desktop, you might have less than optimal results because users can reposition and resize the dialog.

Aside from those few issues, however, it's probably one of those script steps you find yourself sprinkling all around your FileMaker solution. Then, that one day comes, it dawns on you that you'd like to take advantage of that newer FileMaker Card Window option. You'd like to customize your dialogs even further or optionally use a card window for some, and FileMaker's default Show Custom Dialog for others. Then, you find that potentially using a plugin might be a good way to go in some situations as well.

Well, we can plan for all those situations with a little bit of dialog abstraction! This video is for all levels of developers, it's starts out with the basics, but moves on to cover the essentials of dialog abstractions which uses JSON based parameters. I hope this helps address any of your dialoging needs.

Causing a user to make an explicit choice within your software really only happens from some sort of "locked-in" process. This process most typically happens within the form of a dialog box. It's the one roadblock you can stick in front of a user and expect input. Your software then uses that input to determine the output or direction.

While FileMaker Pro does have its own native dialog box, there are some limitations to the native Show Custom Dialog script step. The number one limitation is the lack of control with regards to size and positioning. Aside from that, the dialog box is pretty fixed in terms of how it looks and what it does.

Actually, the limitations on a dialog box are a good thing. It creates a sense of consistency across the whole notion of software itself. Users have seen dialog boxes and interacted with them. They know what they do and how to react to them. So, in order to gain a bit more control and flexibility, we use our own layouts to provide our own variation of a dialog box.

By using a FileMaker layout, we get to control how it looks and reacts to certain situations. This video and technique file revisits an early version which was released when Card Windows had just come out. If you enjoy using powerful and efficient methods of enforcing that "locked-in" process, then make sure to check this one out!