Default Merge Variables

FileMaker 11 introduced the very exciting merge variables feature. Somewhat self-explanatory, in that, you can merge variables into text which is on the layout. This is great, because it will REALLY cut down on the number of calculated fields needed for the user interface. In fact, you could potentially create a whole solution with just data fields and global variables for screen output.

However, there's one GIANT oversight (actually intentional) that really goes against any common sense approach to good UI design. The decision was made to actually show the variable name AS A MERGE FIELD when there's no data in that particular global variable. I mean really, which user ever said "Yeah, I want to see <<$**_developer_variable>> in my layout."

Once again, the thought process behind this was probably along the lines of "Hey, we can't count on your average FileMaker user/developer to remember that the layout should show something, when in fact, there is nothing to show. Why don't we just show the funky looking merge variable as a reminder?". Never mind how much confusion this would lead to for your average end user. I know I would think the database was broken!

Ok, so enough of my rant about this very poor UI decision (yes, my personal, and strong, opinion). Let's solve the problem.

The solution is to create a method where you can actually use this feature, with the peace of mind that the ugly merge variable format won't ever show. Fortunately, with the help of conditional formatting, some creative custom functions and script triggers, this is totally possible! Watch this video for a great solution to using default merge variables. Thanks to Oreste Schiavone for sending in the starter file!

AttachmentSize
DefaultMergeVariables.zip230.63 KB