Qrew LegendThe usual way to do this is to build a table which will be a child table to the table trying to track.
The pipeline triggers when certain fields are modified on the main table, and you create a new record with a pipeline, remembering to connect to the main table by populating related parent. There is syntax in a pipeline to record both the current value of the field, and the previous value of the field.
Would I like to do is to keep the Audit Table very simple and I have a field for the name of the field that was being changed and the old value and the new value. Of course there will be many entries where the old value and the new value is the same depending on how many fields you are trying to track. I filter those off the child Table reports and set up a pipeline to delete those records each night.
Before building another table is it not possible to listen when the status changes and records the current user and date of submission.
Qrew LegendYes, that is easily done. You trigger the pipeline when the status field changes and copy the value of [Last Modified By] into your tracking field as to who made the last change. You can use the Jinja expression. {{time.now}} to populate the date field or else use the [Date Modified] field to populate your Date/Time of the change field.
