Forms will have a difficult time storing the old value without combining a bunch of backwards rules to try and store the current value to some kind of other stored field and then compare if something changed to then store the old value somewhere else. It's odd and not something that I would recommend.
Per your comment Pipelines is the ideal option for this. Your setup would be:
Create a new field to store the old value
In your Pipeline:
Trigger when the record is updated. Include in your field list the value that you want to get the old value for
After your trigger, perform an update record action where you will set the value of the field that will store the old value. In your mapping - you will set the use the $prev syntax to get and populate the prior value of the field retrieved in Step A of your pipeline. So for example if you are getting the value of 'Score' in your trigger, then in your record update you would pass the value of {{a.$prev.score}] as the input to load into your 'old' field.
Hi Chayce,
Thanks for your help. I'm trying to work on this pipeline and got up to the update record action. However, I'm trying to add the new fields (these are the numeric fields that will hold the old value) but they are not showing up on the drop down list.
I've encountered this problem many times when trying to use pipelines and i don't know why this happens. I don't know if I'm doing anything wrong or if there's a workaround I can use. I need the fields to store the old data
Shalom -
Do you have them included in the first step as 'Fields for Subsequent Steps'? Since you're going to be updating the record from the 'Trigger' - you will need to make sure that you include these fields so they can be used in the future steps as well.
So in your trigger, you would include the field that is changing that you want to log as the 'Trigger on Any of these specific fields' - and then below that field for subsequent steps, you would include that field again.
That worked! Thank you
