FileMaker Audit Log

Showcases configuring audit logs by adding core fields: name, first name, address, city, state, zip, phone, email, URL, and company in a managed database, then importing 86 test records.

Explore housekeeping fields that track creation and modification accounts and timestamps for every record, providing record-level auditing in FileMaker, and learn how to enable, customize, or disable them.

Track a small audit trail for a few fields using a calculated field that auto enters the current timestamp, with case logic and the evaluate function.

Enable field level tracking in FileMaker using script triggers to update a timestamp and count field via a company tracking script, evaluating triggers like on object keystroke and exit.

Compare auto enter and script trigger in a FileMaker audit log, highlighting auto enter's schema-level reliability and the layout clutter and conflicts from script triggers.

Learn to implement adaptive set field by name triggers in FileMaker to track fields with one script, reducing clutter while ensuring accurate, fully qualified field references.

Develop a single field tracking approach in FileMaker to log active field changes with timestamp and account name, using append instead of replace for a clean audit trail.

Learn how Get(ModifiedFields) can power a FileMaker audit log by capturing modified fields on record commit and building a timestamped, account name, comma-separated list.

Explore how to remove a tracking field in FileMaker audit logs, including handling field tracking vs modified fields, and using substitution and return management to refine audit data.

Diagnose and fix field tracking in FileMaker by breaking complex tasks into smaller steps, testing progressively, and using the let function to build a solution gradually.

Create an audit table to log every field change as individual records, linking to the source record, with a serial primary key and timestamp sorting for easy reporting.

Create a script to add an audit log record when fields change, linking the contact manager via a foreign key, setting fields and the current timestamp, and preserving context.

Learn to use a new window in FileMaker to preserve context when switching layouts, duplicating scripts, debugging with the script debugger, and auditing the workflow to reduce screen flash.

Choose script triggers for a FileMaker audit log by comparing on object validate and on object save, then apply on object save across fields in the audit table.

Learn the push method in FileMaker Audit Log to push values from a parent to a child without leaving the layout, using a set field and a global id.

Preserve the original field value before changes by capturing it on field focus, storing it in a global variable, and logging both original and changed values in an audit table.

Explore how to build an adaptive FileMaker audit log across multiple tables by leveraging layout, window, and push methods, with generic naming conventions and table-name tracking.

Learn how leading characters in serial numbers differentiate records in FileMaker audit logs, enabling a single foreign key to track both contacts and companies and support precise searches.

Collect field changes into variables and commit multiple audit records to the audit table using a script trigger, avoiding context loss and flashing.

Demonstrates a FileMaker audit log that tracks field modifications, showing how current date, time, and a case statement capture old and new values via log and match fields.

Explore the evolution of the FileMaker audit log into a true single-field logging solution, using a calculated log field, field tracking, and self-referential logging to preserve history.

Build a FileMaker audit log from scratch using a data viewer, dash separators, and an evaluate function to capture timestamped changes by user and field.

Create a centralized, reusable custom function in FileMaker that abstracts logging by concatenating selected fields into a log field and testing it across records.

Explore strategies to prevent editing the log field in FileMaker by switching to view only, using privilege sets, or creating a calculation field to display the log without allowing changes.

Migrate to a table by archiving the found set into archive records linked to the parent, tracking with a Count field, and building values with returns and substitutes.

Analyze the formula in the data viewer, copy and separate values into returns lists to simplify passing the script, then inspect time stamp, who modified, and trend results.

Finishing the migration script, the lecture shows migrating single field logs to a new audits table by counting lines, setting ids and timestamps, looping through records, and testing the results.

Learn how to extend a FileMaker audit log migration by setting the table name, looping through all records in the found set, and archiving them efficiently.

Highlight migrated rows by modifying a calculation field in FileMaker to visually distinguish log lines, using let, left values and right values, and yellow highlight styling.

Use a plug-in to create an audit log in FileMaker, extending capabilities via an API to track edits, deletes, imports, and other events.

Install fmDataGuard as an application-level plugin in FileMaker by quitting the app, placing the plugin in the extensions folder, and enabling it in preferences; launch and verify.

Install fmDataGuard, copy the audit log to the target directory, and connect via an external reference. Configure the two audit fields to reference the primary key.

Learn to implement record-level access and audit logging in FileMaker by configuring security formulas, creating an audit log layout, and applying privilege sets to control access.

Exclude fields in FileMaker data guard logs by using the post edit function, specifying database, table, primary key, and a prefix-based exclude list to omit fields like log.

Explore post delete and post view logging in FileMaker with data guard, compare to post edit, and configure privilege sets to enable secure audits, backups, and rollbacks.

Learn to implement a rollback of audit log entries in FileMaker by calling a simple data guard roll entry function within a script, updating the record with the previous values.

Explore using the FileMaker audit log to roll back a full transaction via transaction IDs, editing only selected fields like address, city, and state, while leaving others intact.

Master rolling back records in FileMaker without plugins by scripting set field by name with fully qualified field names, using audit logs to track original data, changes, and timestamps.

Add a transaction ID to all changes within a single transaction to enable rollback and auditing. Use script triggers and the audit table to assign a unique per record value.

Roll back a transaction in FileMaker by looping through related audits, counting matches by transaction id, and confirming with a dialog before performing the scripted rollback.

Keep a FileMaker solution clean by organizing scripts, layouts, and fields with folders, separators, and notes, hide unused source tables, and tidy relationships for readability.

Access free resources and paid services for filmmaker projects, including blogs, forums, templates, and consulting, plus Udemy courses covering scripting, calculations, relational design, and reporting.