Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
OK, so a no code native solution
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
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
QuickBaseCoachD
8 years agoQrew Captain
OK, let me give you more detail as to how I implemented audit logging for a client on about 15! tables and many fields.
I set up a single table for Audit Logs. They are not actually in a relationship with the tables being logged as I did not want to set up 15 audit logging tables.
I write the values for the table being logged and the field being logged into that Log table. I also record the record ID# field of the record being logged.
If you did want the actual audit logs to appear on the table being logged as an embedded report, you could do that via a report link field. The report link cold be based on a calculated field on the table being logged such as
"Orders-" & [Record ID#]
Then on the audit logging table you would create the same field by formula - the table that the entry was logged from eg "Orders" and the Record ID#
Then you put the report link field on the form and show the records as a report on the form.
I set up a single table for Audit Logs. They are not actually in a relationship with the tables being logged as I did not want to set up 15 audit logging tables.
I write the values for the table being logged and the field being logged into that Log table. I also record the record ID# field of the record being logged.
If you did want the actual audit logs to appear on the table being logged as an embedded report, you could do that via a report link field. The report link cold be based on a calculated field on the table being logged such as
"Orders-" & [Record ID#]
Then on the audit logging table you would create the same field by formula - the table that the entry was logged from eg "Orders" and the Record ID#
Then you put the report link field on the form and show the records as a report on the form.