Are the record's previous values available in the "when record is updated" trigger? I'd like to be able to compare the previous values with the current values and act accordingly. Does this require a code step instead?
Solved
Are the record's previous values available in the "when record is updated" trigger?
+6Best answer by kuovonne
No, the previous values are not available in an automation. This is also true of Airtable scripting. Only current values are available.
One workaround is to use a second editable field in conjunction with the automation to store the "previous value". Set the initial field of this "previous value" field with the current value. When the field is updated, the automation reads the "previous value" field to see what the previous value is, and then the automation copies the current value to the "previous value" field. The "previous value" field and the original field will have the same value, except in the few seconds between when the original field changes and when the automation copies over the value. Because this system does not work well if you need to watch several fields, and it doesn't work well with frequent updates, and it requires more fields, I rarely find it worth implementing.
+29No, the previous values are not available in an automation. This is also true of Airtable scripting. Only current values are available.
One workaround is to use a second editable field in conjunction with the automation to store the "previous value". Set the initial field of this "previous value" field with the current value. When the field is updated, the automation reads the "previous value" field to see what the previous value is, and then the automation copies the current value to the "previous value" field. The "previous value" field and the original field will have the same value, except in the few seconds between when the original field changes and when the automation copies over the value. Because this system does not work well if you need to watch several fields, and it doesn't work well with frequent updates, and it requires more fields, I rarely find it worth implementing.
+6No, the previous values are not available in an automation. This is also true of Airtable scripting. Only current values are available.
One workaround is to use a second editable field in conjunction with the automation to store the "previous value". Set the initial field of this "previous value" field with the current value. When the field is updated, the automation reads the "previous value" field to see what the previous value is, and then the automation copies the current value to the "previous value" field. The "previous value" field and the original field will have the same value, except in the few seconds between when the original field changes and when the automation copies over the value. Because this system does not work well if you need to watch several fields, and it doesn't work well with frequent updates, and it requires more fields, I rarely find it worth implementing.
Thanks.
It would be really helpful to be able to have "before record updated" event (or similar) that had previous and new values for the monitored fields.
+35As @kuovonne mentioned, the only way to do this in Airtable is through automations, but it is generally problematic as Kuovonne mentioned, so it is not typically recommended.
if you really need this feature, you would need to switch to a more advanced database app that natively supports this feature as a built-in part of the app, such as Claris FileMaker.
I used to be a FileMaker Developer for almost 30 years before becoming an Airtable consultant. Feel free to reach out to me through my website if you’d like me to turn you onto some excellent FileMaker developers.
+3No, the previous values are not available in an automation. This is also true of Airtable scripting. Only current values are available.
One workaround is to use a second editable field in conjunction with the automation to store the "previous value". Set the initial field of this "previous value" field with the current value. When the field is updated, the automation reads the "previous value" field to see what the previous value is, and then the automation copies the current value to the "previous value" field. The "previous value" field and the original field will have the same value, except in the few seconds between when the original field changes and when the automation copies over the value. Because this system does not work well if you need to watch several fields, and it doesn't work well with frequent updates, and it requires more fields, I rarely find it worth implementing.
Hi, can you give examples of how to do this? The before (previous) date and the new/after date in a date field. Actual code in an automation.
thanks
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.