Forum Discussion
Make a child table of Audit Logs for the table you are tracking
Make fields for User (type User) date/time, old value, new value, and field name.
Then have an action that fires where the record is changed and [Field 1 changes]
The action will be to add an audit log record and you will map the values or the old values into the various fields. Be sure to map [Last modified by] into the User field - that is who made the change.
Read up about Actions if you have not used them before. https://help.quickbase.com/user-assistance/creating_a_quickbase_action.html
This is clicking a bit more for me. I can see where this is going with how it functions a little better.
Quick question though, you say "create a child table of Audit Logs for the table you are tracking". I need to track from multiple tables, two currently with the possibility of a third we planned to add. Will I need to create more than one child table for audit logs. Or can I simply map or build relationships between my Audit Log table fields to fields in both my Customers table & fields in my Support tasks table?
Customer (Parent Table) - = Support Tasks (Child Table)
Customer - = Slow Pay Tasks (Child Table - Potential NEW table)
------
Audit Log (Child Table)
Fields: User, Date/Time, Old Value, New Value, Field Name (Mapped to Field in Table I'm tracking?)
-----
For some context here some examples of the fields and tables I need to track.
Support Task Table - Fields: Start Date, Sent Date, Finished Date, On Hold (Checkbox), Cancelled (Text Drop Down)
Customer Table - Fields: Agent Assigned (Text Dropdown), Renewal Date, Renewal Amount (Numeric), Contact Date, Contact Type (Radials / Checkbox)
I think I will give this a try as it seems a little more simplistic before I resort to Joshua's method. Your time is greatly appreciated. Hope I explained this properly.