Within the world of FileMaker development, there are always those golden gems which become the hallmarks of "how to do something" - despite there often being more than one way to solve a problem. For managing lists of data, prior to the existence of the While function, the go-to custom function is CustomList. When it comes to variable output display using a portal you'll almost always reference Virtual List as the commonly understood approach.
When it comes to saving user state, there's always been a number of ways accomplish this. But, for my part, I'm going to declare Layout Variables as the way to solve many issues when it comes to saving user state in FileMaker.
While the term "Layout Variables" can apply to either locally scoped variables or global ones used within the layout, the concept is such that you're using variables to store things for the specific layout the user is on. When it comes to saving state, whether for the specific session or in order to persist, there has to be a simple and easy way to store, reference and retrieve these values and I think that solution is finally here. In this video, I showcase the Custom Functions and methods I use to implement Layout Variables.
If your FileMaker solution has a need to maintain state and make it easy to both store and restore global variables used for the user interface, then you simply must watch this video.
Click the title or link to this article to view the video.