Qrew LegendThis should be no problem for the pipeline.
Trigger the pipeline based on the status change and the have a create record step to populate the old stage and the new stage.
Initially drag the stage field into both fields on the audit record (old and new values) .
Then edit the box with the </> icon to see the code and insert $prev into the code.
{{a.$prev.Stage}}
Hi Mark
I can copy the stage values but not the fields on the form. When the button is clicked it updates the record with new stage. But the metadata of all other fields that were modified before this stage update (through button) is lost.
Qrew Legendwell, you will need to trigger on any field that could be edited which you need tracked. You will have a design issue as to if the audit log record will have the field name and the old value and the new value, or if it will be a really "wide" record with say 10 field names and 10 old values and 10 new values. If you go the former route, you will need to have either multiple pipelines (yuk) or else a pipeline that will have a step per tracked field. That will result in many records being created in the audit log when no change happened to have happened on that field, but you can filter those off reports where old and new values are the same, andhave a process to auto delete them each night or even as the last step of the pipeline ... ie search for records to be deleted where old and new are the same.
I prefer the narrow audit table with a record per field changed
