Skip to main content
Question

New Form - Rule Trigger for Field Value Change OR accessing old value?

  • June 19, 2023
  • 0 replies
  • 741 views

Context:   In old forms I had a rule that that would WRITE the old status to a log field when the user CHANGED the status of a transaction. (e.g. New to Complete, New to Hold, etc.). This was achieved by using a dynamic form rule triggered on the field value change upon SAVE. 

Additional Note: Thanks to @Mark Shnier (Your Quickbase Coach) post about "$prev." in Jinja I know we can do it there in a pipeline - but that isn't a desirable method. 

Possible Work Around in New Forms: Use the old form or create a pipeline on record save and use $prev. I tried playing around with New Forms rules formula builder - but still seem to lack a way to access the OLD Field Value and an Action trigger. 

Wasn't there some way to access an old field value within a formula so that I could use the New Form rules formula builder to create a boolean for   [Status] <> [old.Status] as a trigger? 



------------------------------
joe vandervest
------------------------------

AdamKrzyzanek
Forum|alt.badge.img+10

I believe you just need to change setting of this Form Rule and un-check "Run change action when a condition changes from false to true".




------------------------------
Adam Krzyzanek
------------------------------

Forum|alt.badge.img+2
  • Registered
  • November 21, 2025

I'm also here checking in if there is a way to perform an action with new form rules when a field's value has changed...surely there must be a way?


curevick
Forum|alt.badge.img+5
  • Registered
  • November 23, 2025

I’d also be super curious to see the full setup with some screenshots of the form. To Mark’s point, a helper field combined with two form rules could get you where you need to go. You could simulate “this field has changed” by populating a helper field under a certain condition and then comparing it to the main field in another rule to trigger the action you need.