Brief Introduction
Creating an Audit Log in FileMakerDescription
Audit logs track field and record modifications so changes can be rolled-back or forward. In FileMaker, changes can be tracked many ways, each with it's own advantages and disadvantages. We'll walk you through every technique out there in the FileMaker world and talk about when to use each solution. By the time you're done, you'll have learned tons about scripting, calculations and relational design. Before starting this course, make sure you are at an intermediate programming level for FileMaker which includes familiarity with scripting, calculations and relational design.
Requirements
- Requirements
- Students should be at or close to an intermediate level of FileMaker programming including familiarity with layout mode, scripting, relational design and calculations
- The course is taught using FileMaker 17 but can be taken by any with FileMaker 13 or later
Knowledge
- How to create an audit log in FileMaker
- Scripting
- Calculations
- Set Field: Push and Pull
- Auto-Enter Calculations
- Housekeeping fields
- Calculated field tracking
- Scripted field tracking
- New window techniques
- Set Variable
- Support for multiple audited tables
- Abstraction
- fmDataGuard plug-in
- Roll-Back
- Roll-Forward
- Migrating data from a single field to a table
John Mark Osborne
4.5 Raiting
FileMaker Audit Log
- 4.5
-
![]()
![]()
![]()
![]()
![]()
Creating an Audit Log in FileMaker Audit logs track field and record modifications so changes can be rolled-back or forward. How to create an audit log in FileMaker...
