The Separation Model – Part 15 – Maintain Layout State

Nobody likes a rug being yanked out from underneath them - to reference the popular phrase. The same thing applies to your interface and solution. When a user moves from one layout to another, they're typically not expecting to come back to something different than when they left.

The biggest issues with FileMaker retaining layout state are tabs and portals. In the past, I've covered how you can move from one record to another and maintain the selected portal row.

In this video, I present a simple technique for using the ever popular "back button" feature found in pretty much every web browser. The video shows how to not only include this feature, but also how you can return tabs to their previously selected state - and with very simple scripts.

If you've rarely found great uses for FileMaker's script triggers, then this video will provide you with some great information about using them.

For any of the functions referenced, you can find them here.
https://github.com/filemakerstandards/fmpstandards/tree/master/Functions

Comments

You mentioned that on video 15 of the data separation model that the file will be with it but i dont see it.

Mark Johnson
Aroma Impressions
mark@aromaimpressions.com

I am having an issue in my solution where the last tab is not being saved when the "Previous Layout" script is run. The layout name is only being captured.

In the Data Viewer, it shows this:

Reports|
Schedule|
Customers|
Schedule|
Customers|

Notice that the tab names are missing...Why would this be?