Skip to main content
Question

Using one field to collect data multiple times.

  • Jun 29, 2026 10:04 AM UTC
  • 1 reply
  • 60 views

RoyWanyoike
Forum|alt.badge.img+13

In quickbase, I have a field for user and datetime. There are several project status like pending, submitted, review,approved and denied. 
Everytime in the status field change I want to record who did the change and date time. I want to use the two buttons. submitted by and submitted datetime field to track the audit history or logs. I did try with a pipeline but there is no data being recorded. Anyone done this before?

1 reply

Top Step
Forum|alt.badge.img+12
  • Observing
  • Oct 15, 2026 4:18 PM UTC

Two fields on the same record can't keep every past change — each save overwrites them. For a real audit trail you want a child History (or Status Log) table, and a pipeline that writes a new child row whenever Status changes.

Use an On New Event trigger on the project table. Set Trigger on Any Field to No, then Trigger on Any of These Specific Fields to Status (and any other fields you care about). Turn On Modify Record on. That way it only fires when Status actually changes.

In the Create Record step on the History table, map Related Project, current Status, Modified By, and Date Modified from the trigger. For the previous status use $prev:

{{a.$prev.status}}

If the pipeline ran but wrote nothing, the usual causes are triggering on every field (so you filtered it away), missing Status in Specify Fields for Use in Subsequent Steps, or writing back to the same two fields on the parent instead of creating a child.

If you only need a running text log and not a reportable history table, a Text - Multi-line field with "Log the edits to this field" turned on will append each edit with the user and timestamp on the form.

https://help.quickbase.com/docs/creating-data-change-logs-using-pipelines 

https://help.quickbase.com/docs/use-the-quickbase-channel 

https://help.quickbase.com/docs/logging-text-field-edits