Content Revisions

by Matt Petrowsky

Article options

• Watch Preview Video
• Watch Full Version
• Download Movie File

Many FileMaker solutions ultimately end up adding some form of an audit trail. An audit trail is a great solution when you need to rigorously track what has been done to pretty much any field within the database.

Of course, you can always selectively choose what to track and that's where you start to distinguish between content revisions and audit trails. In the case of a content revision, you know there is a specific piece or chunk of information in which you want to see the history of evolution for that information.

In my case, this comes in the form of a comment being left about a particular FileMaker technique. Wanting to know if it has been edited and what specifically the changes were. For you it may be comments, notes (same thing essentially) or full blown document revisions.

While there are solutions out there which provide comprehensive external document tracking, there are certainly times when you want to manage and track revisions to just one or a few fields.

This video shows you what you need to know in order to take advantage of FileMaker's own default tools in order to facilitate content revisions.